# CVE-2026-26396: Path traversal in n/a

> Attackers can read arbitrary files via path traversal in XAgent, leading to sensitive information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-c52p-2jm8-wv9q

## What is CVE-2026-26396?

CVE-2026-26396 is a high-severity path traversal vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenBMB XAgent v1.0.0 and before is vulnerable to path traversal in the file() function in XAgent/XAgentServer/application/routers/workspace.py. The input parameter “filename” is user-controllable and is concatenated into the file path to be read without proper validation, leading to a directory traversal vulnerability that may result in sensitive information disclosure.

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

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


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

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

## Is CVE-2026-26396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26396 is a high-severity path traversal vulnerability in n/a, published on 13 Jul 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-26396 exists.

Affected product: n/a. 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-26396/ (Markdown: https://insights.sbomify.com/CVE-2026-26396/index.md)
```

## Sources

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

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