CVE-2026-74038: Wazuh 4.0.0 before 4.14.6 contains a path traversal vulnerability that allows unauthenticated remote attackers to…

CVE-2026-74038 · Severity: high · CVSS 7.1 · Published 2026-08-18

Wazuh 4.0.0 before 4.14.6 contains a path traversal vulnerability that allows unauthenticated remote attackers to cause denial of service by enrolling an agent with a dot-sequence name such as ".." through the enrollment port. Attackers exploit insufficient validation in OS_IsValidName() and unsafe path concatenation in delete_diff() to resolve the traversal to the parent queue directory, causing its subdirectories to be removed and stopping all Wazuh services requiring manual recovery.

Technologies: Wazuh. Vendors: Wazuh.

Quick answers

Is CVE-2026-74038 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-74038 being exploited in the wild.
How severe is CVE-2026-74038?
High severity, with a CVSS score of 7.1, published 18 August 2026.
Which products and versions are affected?
Wazuh. The advisory does not name versions.
Is there a fix for CVE-2026-74038?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-74038?
Check whether you run Wazuh. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Wazuh

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.