XROOTD · CVE-2026-125113 · Package
FIX → 5.9.2
XRootD lets a remote user list the parent directory of an exported path by appending '/..' to the path in xrdfs ls or HTTP PROPFIND requests. The listing reveals names of unexported files and directories, but the sources say file download through this path is blocked.
first public Apr 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Deployments of the XRootD server with an exported path restricted by all.export are exposed to directory and filename enumeration over xrdfs or HTTP. The sources say the flaw applies regardless of authentication configuration. Python packages that only use the client side of xrootd are not described as affected.
Not affected if no-xrootd-server
Who cares http, python, self-hosted, xrootd
python -c "import xrootd; print(xrootd.__version__)" or pip show xrootdall.export in the xrootd configuration file to see which paths are exported/.. returns a listing, using a server you ownUpgrade to 5.9.2
A path traversal vulnerability in XRootD allows users to escape the exported directory scope and enumerate the contents of the parent directory by appending /.. (specifically without trailing slash) to an exported path in xrdfs ls or HTTP PROPFIND requests.
This bypass ignores the all.export restriction.
src/XrdXrootd/XrdXrootdXeq.cc, and more precisely the functions rpCheck() and Squash() used in do_Dirlist() (link), as they do not check if the path ends with ".." (without trailing slash).
Then the path is passed directly to the filesystem layer.
xrd.port 1094
# Exposing only /alice/
oss.localroot /srv/xrootd/data/
all.export /alice/
# HTTP
xrd.protocol http:1094 libXrdHttp.so
# Logs / monitoring
all.adminpath /var/spool/xrootd
all.pidpath /var/run/xrootd
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
xrootd (PyPI): move to 5.9.2 or later/srv/xrootd/data/
├── alice/ ← only exported directory
├── bob/ ← not exported
└── secret.txt ← not exported
xrootd -c /etc/xrootd/xrootd.cfgNormal behavior (access outside export is denied):
$ xrdfs root://<xrootd-server> ls /
[ERROR] Server responded with an error: [3010] Stating path '/' is disallowed.
Bypass via trailing ..:
$ xrdfs root://<xrootd-server>ls /alice/..
/alice/../alice
/alice/../bob
/alice/../secret.txt
Also exploitable via HTTP PROPFIND:
curl -X PROPFIND 'http://<xrootd-server>:1094/alice/..' \
--path-as-is \
-H "Depth: 1"
Returns HTTP 200 with full listing of the parent directory, including unexported entries (bob/, secret.txt).
However, file download via this path traversal is blocked:
$ xrdcp root://<xrootd-server>/alice/../secret.txt .
[0B/0B][100%][==================================================][0B/s]
Run: [ERROR] Server responded with an error: [3010] Opening relative path 'alice/../secret.txt' is disallowed. (source)
An attacker can enumerate directories and filenames outside the authorized export scope defined by all.export. In the example above, a server exporting only /alice/ leaks the existence of /bob/ and secret.txt located in the parent directory (oss.localroot).
File download is not possible through this vector, as xrdcp correctly rejects the path with error 3010. The impact seems therefore limited to information disclosure (directory and filename enumeration).
This vulnerability could affect all XRootD deployments regardless of authentication configuration, as it bypasses the export path restriction itself.
In rpCheck() (src/XrdXrootd/XrdXrootdXeq.cc), change:
// Before
if (fn[0] == '.' && fn[1] == '.' && fn[2] == '/') return 1;
// After
if (fn[0] == '.' && fn[1] == '.' && (fn[2] == '/' || fn[2] == '\0')) return 1;
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.