Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable endpoint requires low-privilege authenticated account with allow_run_as; only availability is impacted with unchanged scope.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
Wazuh 4.0.0 before 4.14.7 and 5.0.0-beta2 contain a denial of service vulnerability that allows authenticated attackers with allow_run_as enabled to exhaust CPU resources by submitting arbitrarily deeply nested JSON structures to the POST /security/user/authenticate/run_as endpoint. Attackers can repeatedly submit malformed auth_context bodies with unlimited nesting depth to cause the API framework to consume excessive CPU, denying service to all other API consumers.
AnalysisAI
CPU exhaustion in Wazuh Manager 4.0.0-4.14.6 and 5.0.0-beta2 allows authenticated API users with the allow_run_as permission to fully deny service to all other API consumers by submitting arbitrarily deeply nested JSON to the POST /security/user/authenticate/run_as endpoint. The API framework processes these structures recursively without any depth or size limit, consuming CPU proportionally to nesting depth until the process becomes unresponsive. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Two conditions must both be true: (1) the attacker must hold a valid Wazuh API credential - exploitation is authenticated, PR:L per the CVSS 4.0 vector; and (2) the allow_run_as flag must be explicitly enabled for that account in Wazuh RBAC configuration - this is a non-default, operator-configured permission. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 4.0 scores this 7.1 with AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H, accurately reflecting that the endpoint is network-reachable, requires only low-privilege credentials (an authenticated account with allow_run_as), and produces high availability impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker holding a Wazuh API account with allow_run_as enabled sends a loop of POST /security/user/authenticate/run_as requests, each with a JSON body containing thousands of levels of nesting such as {"a":{"a":{"a":...}}}. The API framework recursively traverses the full structure on every request with no depth bound, pegging CPU on the Wazuh Manager process. … |
| Remediation | Upgrade Wazuh Manager to version 4.14.7 or later; the CVE description boundary confirms 4.14.7 as the fixed release. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all Wazuh Manager instances running versions 4.0.0-4.14.6 or 5.0.0-beta2, document which API users possess the allow_run_as permission, and review API logs for unusual deeply nested JSON submissions to POST /security/user/authenticate/run_as. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Wazuh Manager
View allMultiple shell injection and untrusted search path vulnerabilities in Wazuh agent and manager (versions 2.1.0 through 4.
Path traversal via unsanitized cluster node names in Wazuh Manager 4.0.0 through 4.14.5 enables authenticated cluster pe
Path traversal in Wazuh Manager 4.0.0 through 4.14.5 allows unauthenticated remote attackers to destroy the manager's qu
Wazuh Manager authd service through version 4.7.3 fails to properly restrict client-initiated SSL/TLS renegotiation requ
Memory exhaustion in Wazuh Manager 4.4.0 through 4.14.6 allows authenticated cluster peers to crash the wazuh-clusterd d
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-61075