# CVE-2026-93347: Wazuh 4.1.1 before 4.14.8 Path Traversal via Cluster get_list_file

> Malicious cluster workers with the cluster key can read arbitrary files via path traversal in the get_list_file helper.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-xrjw-cqrv-j92g

## What is CVE-2026-93347?

CVE-2026-93347 is a medium-severity path traversal vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Wazuh from 4.1.1 before 4.14.8 contains a path traversal vulnerability in the get_list_file helper that allows malicious cluster workers to read arbitrary files via unvalidated filename values. Attackers holding the cluster key can send DistributedAPI requests with traversal filenames to read client.keys, ossec.conf with the cluster key, and other wazuh-readable files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-93347 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93347 is a medium-severity path traversal vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93347 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-93347/ (Markdown: https://insights.sbomify.com/CVE-2026-93347/index.md)
```

## Sources

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

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