Skip to main content
VulnerabilityPublished Updated

CVE-2026-74039: wazuh-manager · Unthrottled Resource Allocation

Affects wazuh-managerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.14.7 soon.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.14.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade wazuh-manager to 4.14.7.

Affected software

ProductAffectedFixed in
Wazuhwazuh-managerAffected
  • >=4.0.0 <4.14.7
  • =5.0.0-beta2
Fixed in
  • 4.14.7
GitHubwazuh-managerpkg:github/wazuh-managerOther threatsAffected
  • >=4.0.0 <4.14.7
  • =5.0.0-beta2
Fixed in
  • 4.14.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict or disable the allow_run_as feature for users who do not require it to reduce exposure. Monitor and limit the complexity of JSON payloads submitted to the affected endpoint if possible.

Description

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.

References

Community reviews

Loading reviews…