# CVE-2026-72572: o1lab xmysql - Unauthenticated Path Traversal via name Query Parameter

> Unauthenticated attackers can read arbitrary files from the server via path traversal in the name query parameter of the xmysql library.

- **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:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-9pgj-cxw3-gw33

## What is CVE-2026-72572?

CVE-2026-72572 is a high-severity path traversal vulnerability in o1lab xmysql, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability in o1lab/xmysql (all versions) allows an unauthenticated remote attacker to read and download arbitrary files from the server. The lib/xapi.js file at lines 338 and 424 uses the user-controlled req.query.name parameter in path.join(cwd, name) without sanitization before passing it to res.download, enabling directory traversal via ../ sequences to access sensitive system files.

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

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


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

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

## Is CVE-2026-72572 being exploited?

There is no known exploitation of CVE-2026-72572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72572 is a high-severity path traversal vulnerability in o1lab xmysql, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72572 in the wild and no public exploit code.

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

## Sources

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

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