wazuh-manager: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-74038 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in wazuh-manager from Wazuh, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 4.14.6 as the first without the flaw, so updating wazuh-manager to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.55% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update wazuh-manager to 4.14.6 or a later version.
- Update Wazuh to 4.14.6 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Wazuh | wazuh-manager | 4.0.0 up to, but not including, 4.14.6 | 4.14.6 |
| Wazuh | Wazuh | 4.0.0 up to, but not including, 4.14.6 | 4.14.6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.0 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.1 | High | CNA (vulncheck.com) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/wazuh/wazuh/security/advisories/GHSA-573w-mqw4-jvmrExploit, Mitigation
Patches and release notes
- github.com/wazuh/wazuh/pull/35833Issue Tracking
Third-party and government advisories
- vulncheck.com/advisories/wazuh-path-traversal-dos-via-agent-enrollmentThird Party Advisory
Other vulnerabilities in wazuh-manager
- 7.1 High severity
- 9.0 Critical severity
- 7.2 High severity
- 9.1 Critical severity
- 7.2 High severity
- 7.2 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.4 High severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.