CVE-2026-74039
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.1
- CVSS vector
- 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
- EPSS probability
- 0.36%
- CWE
- CWE-770, CWE-1333
- Published
- 2026-08-18
- Last modified
- 2026-08-18
Affected products
- Wazuh wazuh-manager
- Wazuh wazuh-manager
Weakness type
Related vulnerabilities
- CVE-2026-87908 — multiparty vulnerable to Denial of Service via unbounded part-header accumulation
- CVE-2026-45769 — ikev2: unbounded client transform storage can lead to resource exhaustion
- CVE-2026-45768 — Suricata ldap: unbounded responses per transaction can lead to resource exhaustion
- CVE-2026-45766 — Suricata nfs: unbounded stateful structures can lead to resource exhaustion
- CVE-2026-45765 — Suricata dnp3: unbounded reassembly can lead to resource exhaustion
- CVE-2026-88012 — Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded
- CVE-2026-45763 — Suricata lua: sandbox allocation limit not enforced for new allocations
- CVE-2026-88878 — Traefik v2.8.2 through v3.6 HTTP/3 Timeout Bypass