CVE-2026-74032
Received Received - Intake

Authorization Bypass in Wazuh via Unprotected RBAC Endpoints

Vulnerability report for CVE-2026-74032, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-13

Last updated on: 2026-10-13

Assigner: VulnCheck

Description

Wazuh from 4.0.0 before 4.14.8 contains an authorization bypass vulnerability that allows low-privileged authenticated users to read the RBAC catalog by querying unprotected security endpoints. Attackers can request GET /security/actions and /security/resources, which omit the caller's RBAC policies, to map privileged actions and endpoints for privilege escalation planning.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-13
Last Modified
2026-10-13
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Wazuh wazuh-manager 4.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-74032 is an authorization bypass vulnerability in Wazuh versions 4.0.0 to 4.14.7. It allows low-privileged authenticated users to read the RBAC catalog by querying unprotected security endpoints like GET /security/actions and GET /security/resources. These endpoints omit the caller's RBAC policies, exposing privileged actions and enabling privilege escalation planning.

Detection Guidance

To detect this vulnerability, check if your Wazuh API endpoints /security/actions and /security/resources return RBAC data to low-privilege users. Use curl commands like: curl -k -u user:password https://<wazuh-server>/security/actions and curl -k -u user:password https://<wazuh-server>/security/resources. If these return 200 OK with RBAC details instead of 403 Forbidden, the system is vulnerable.

Compare responses between /security/config (should return 403) and the affected endpoints. Vulnerable systems will show exposed RBAC mappings.

Impact Analysis

An attacker with low privileges could exploit this to map out privileged actions and endpoints in the Wazuh API. This information could then be used to plan further attacks, such as privilege escalation, potentially gaining unauthorized access to sensitive data or system functions.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Exposure of RBAC catalogs may result in non-compliance with data protection and access control regulations, potentially leading to legal and financial penalties.

Mitigation Strategies

Upgrade Wazuh to version 4.14.8 or later immediately. If upgrading is not possible, restrict access to the /security/actions and /security/resources endpoints via network controls or API gateways until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74032. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart