# CVE-2026-72713: XAgent Path Traversal Arbitrary File Read via /workspace/file

> Attackers can read arbitrary host files, including secrets, by exploiting a path traversal flaw in the workspace file endpoint.

- **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:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-c7q4-h75g-2c94

## What is CVE-2026-72713?

CVE-2026-72713 is a high-severity path traversal vulnerability in OpenBMB XAgent, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XAgent contains a path traversal vulnerability in the workspace file endpoint that allows self-registered or default-credential users to read arbitrary files on the host by supplying parent-directory segments in the `file_name` form field with no path containment check. Attackers can register an account without email verification, then submit crafted `file_name` values such as parent-directory traversal sequences to the `/workspace/file` handler to read host files including application secrets, database credentials, and system files outside the Docker sandbox.

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

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


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

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

## Is CVE-2026-72713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72713 is a high-severity path traversal vulnerability in OpenBMB XAgent, published on 11 Aug 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-72713 exists.

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

## Sources

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

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