# CVE-2026-74034: Wazuh 4.1.0 before 4.14.8 Arbitrary File Read via upgrade_custom Command

> Enrolled agents can exploit a missing origin check to read arbitrary files as root, potentially exposing sensitive system credentials.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-r7hm-43xr-477j

## What is CVE-2026-74034?

CVE-2026-74034 is a high-severity path traversal vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wazuh from 4.1.0 before 4.14.8 contains a missing origin check in wm_agent_upgrade that allows enrolled agents to issue upgrade_custom commands with attacker-controlled file_path. Attackers can inject an upgrade_custom message over the agent channel to read arbitrary files as root, exfiltrating /etc/shadow and client.keys.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-74034?


## How do I fix CVE-2026-74034?

No fix has been published for CVE-2026-74034 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-74034 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74034 exists.

Public exploit code:

- Wazuh PoC chaining CVE-2026-74034 file read and CVE-2026-74041 command execution; fixed in 4.14.8. Python standard library only. (github_poc): https://github.com/roninreilly/wazuh-unauth-chain

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74034 and fix it if it is affected.

What it is: CVE-2026-74034 is a high-severity path traversal vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74034 exists.

Affected product: wazuh-manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74034/ (Markdown: https://insights.sbomify.com/CVE-2026-74034/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74034
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74034
- OSV: https://osv.dev/vulnerability/CVE-2026-74034

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74034/
Summaries are generated and may contain mistakes; the official description above is the record.