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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/wazuh/wazuh/pull/37034 Issue Tracking, Patch
- https://github.com/wazuh/wazuh/security/advisories/GHSA-5vh8-34r8-q74q Exploit, Mitigation, Vendor Advisory
- https://github.com/wazuh/wazuh/security/advisories/GHSA-5vh8-34r8-q74q Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.1 · wazuhNVD modified 2026-10-22 22:10
Affected (CPE criteria) 3
cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*cpe:2.3:a:wazuh:wazuh:5.0.0:beta1:*:*:*:*:*:*cpe:2.3:a:wazuh:wazuh:5.0.0:beta2:*:*:*:*:*:*
References 4
- https://github.com/wazuh/wazuh/pull/37034 Issue Tracking, Patch
- https://github.com/wazuh/wazuh/security/advisories/GHSA-5vh8-34r8-q74q Exploit, Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/wazuh-api-dos-via-deeply-nested-json-auth-context Third Party Advisory
- https://github.com/wazuh/wazuh/security/advisories/GHSA-5vh8-34r8-q74q Exploit, Mitigation, Vendor Advisory