Vulnerability in Wazuh (CVE-2026-74039)
Summary
Vulnerability in Wazuh (CVE-2026-74039). Risk of unauthorized operations or information disclosure. Exploitable via POST /security/user/authenticate/run_as.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-74039 has been found in Wazuh.
Attackers can target a specific entry point like POST /security/user/authenticate/run_as over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Wazuh CVE-2026-74039" on the vendor's site.
CVE-2026-74039 (Wazuh) — CWE-770 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /security/user/authenticate/run_as
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in Wazuh. Attackers reach the vulnerable code path via POST /security/user/authenticate/run_as.
Check the vendor advisory for the affected versions of Wazuh. Attack surface: POST /security/user/authenticate/run_as.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /security/user/authenticate/run_as requests with malformed payloads or SQL meta-characters. Run grep -r 'Wazuh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Wazuh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Wazuhを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /security/user/authenticate/run_as' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /security/user/authenticate/run_asへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /security/user/authenticate/run_as on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory disclosure@vulncheck.com
- exploit github.com
- patch disclosure@vulncheck.com