XRootD: Path traversal in directory listing allows access to the parent directory via trailing ".." pattern
- Exploited
- No known exploitation
- Fix
- Fixed in 5.9.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.9.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
XRootD, a data-handling and storage system, has a path traversal flaw in its directory listing that lets an attacker read directory and file names in the parent directory of an exported path. It can be reached remotely, without logging in, by appending a trailing "/.." to an exported path in a listing request.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.9.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- xrootd xrootd
fixed in 5.9.2
- xrootdPyPI
fixed in 5.9.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125113
Is CVE-2026-125113 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125113?
xrootd: before 5.9.2. xrootd (PyPI): before 5.9.2.Source: cve.now feed data
How do I fix CVE-2026-125113?
Upgrade to a fixed version: 5.9.2.Source: cve.now feed data