November 14, 2026

CVE Watchtower

CVE-2026-125113Improper Input Validation

NVDCVSS scored by security-advisories@github.com

Vulnerability Summary

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.
Severity Level
MEDIUM(5.3)
Published Date
Nov 9, 2026
Last Modified
Nov 12, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Published
EPSS Score (30-Day)
0.34%Probability
Root Weakness (CWE)
CWE-20: Improper Input Validation β†—
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required.
CWE-22: Path Traversal β†—
The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory.
CVSS v3.1 Base Metrics — Score 5.3 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

Affected & Patched Versions

Affected Versions
Not provided by NVD for this CVE.
Patched Versions
No patched version published yet
Until a fix ships, reduce exposure:
  • Restrict access to the affected service or interface to trusted networks.
  • Disable the affected feature if you do not need it.
  • Watch the vendor advisory for a firmware or software update.

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run the affected product and which version.
  2. No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
  3. Subscribe to the vendor advisory so you learn when a fix ships.

Timeline

  • Nov 9, 2026Published
  • Nov 12, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get alerts for CVEs like this oneYou are reading CVE-2026-125113. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

External References

Data last checked: Nov 9, 2026 23:10 UTC