# CVE-2026-125113: XRootD: Path traversal in directory listing allows access to the parent directory via trailing ".." pattern


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-vj8v-p5vw-m6v5, UBUNTU-CVE-2026-125113

## What is CVE-2026-125113?

CVE-2026-125113 is a medium-severity vulnerability in xrootd, published on 9 Nov 2026. 

### Official description

The XRootD project provides a high-performance, fault-tolerant, and secure solution for handling large amounts of data distributed across multiple storage resources. Prior to version 5.9.2, XRootD's rpCheck() function in src/XrdXrootd/XrdXrootdXeq.cc rejects a parent-directory component only when two dots are followed by a slash and does not reject a terminal two-dot component. An unauthenticated attacker can append /.. to an exported path in xrdfs ls or an HTTP PROPFIND request, bypass the all.export directory scope, and cause directory and filename enumeration in the parent directory under oss.localroot. The demonstrated vector does not permit file download or disclose file contents. This issue is fixed in version 5.9.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-20 (Improper Input Validation)

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

1 open source package ship an affected version, including xrootd.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xrootd` | PyPI | All versions | 5.9.2 |

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

Upgrade xrootd to 5.9.2 or later.

## Is CVE-2026-125113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125113 is a medium-severity vulnerability in xrootd, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125113 exists.

Affected packages and fixed versions:
- xrootd (PyPI): affected all versions; fixed in 5.9.2

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-125113/ (Markdown: https://insights.sbomify.com/CVE-2026-125113/index.md)
```

## Sources

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

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