CVE-2026-74039Public exploitNetwork attack vector

Authenticated service interrupt via auth_context recursion

Published Aug 18, 2026 · Updated Aug 18, 2026

Denial of service in Wazuh manager before 4.14.7 and 5.0.0-beta2 allows remote authenticated users to stall API authentication. The POST /security/user/authenticate/run_as path recursively walks attacker-supplied auth_context JSON, applies role-defined regular expressions without a timeout, and runs that work through a single-worker authentication pool. Exploitation requires credentials with allow_run_as enabled; repeated deeply nested or oversized requests can monopolize authentication handling and deny service to other API consumers without published evidence of data read or modification.

CVSS severity7.1
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in Wazuh manager before 4.14.7 and 5.0.0-beta2 allows remote authenticated users to stall API authentication. The POST /security/user/authenticate/run_as path recursively walks attacker-supplied auth_context JSON, applies role-defined regular expressions without a timeout, and runs that work through a single-worker authentication pool. Exploitation requires credentials with allow_run_as enabled; repeated deeply nested or oversized requests can monopolize authentication handling and deny service to other API consumers without published evidence of data read or modification.

The record

CVE
CVE-2026-74039
Published
Aug 18, 2026
Updated
Aug 18, 2026
Vendor
Wazuh
Product
Wazuh manager
Classifications
CWE-770, CWE-1333, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.0.0 <4.14.7
  2. Affected versionversion=5.0.0-beta2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuh managerversion=4.0.0 <4.14.7; version=5.0.0-beta2

Published CVSS scores

7.1VulnCheck CNACVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
6.5GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-770Allocation of Resources Without Limits or Throttling
CWE-1333Inefficient Regular Expression Complexity
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo