CVE-2026-74039

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of service disruption.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-18 18:19 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-22 22:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 7.1 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-08-18 18:19 UTC

Last modified

2026-10-22 22:10 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-770 · Allocation without limits

Record status

Analyzed

Affected

• Wazuh < 4.14.7
• Wazuh 5.0.0

Attack profile CVSS 4.0 · 7.1

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-74039.md and follow it. Check whether this project is affected by CVE-2026-74039. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge