Quick answers
- Is CVE-2026-72713 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72713 being exploited in the wild.
- How severe is CVE-2026-72713?
- High severity, with a CVSS score of 7.5, published 11 August 2026.
- Which products and versions are affected?
- OpenBMB XAgent <UNKNOWN>.
- Is there a fix for CVE-2026-72713?
- A patch was published on 2026-07-31. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72713 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72713?
- Check whether you run OpenBMB XAgent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal flaw in the `/workspace/file` HTTP endpoint that fails to validate or sanitize the `file_name` form parameter. Unauthenticated attackers can self-register an account without email verification, then submit crafted file names containing parent-directory traversal sequences (e.g., `../../../etc/passwd`) to access files outside the intended workspace directory. The lack of path containment validation allows reading arbitrary files on the host, including files outside the Docker sandbox. A fix was published on 2026-07-31 in commit 26f2b6edc75127af524f027c022b382967178e3a.
Affected products
- OpenBMB XAgent <UNKNOWN>
Timeline
- 2026-08-11: disclosed
- 2026-07-31: patched