GHSA-pgf8-28gg-vpr6 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in @backstage/techdocs-common. A fix is available for @backstage/techdocs-common — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@backstage/techdocs-commonnpmDescription
Impact
A malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for docs_dir in mkdocs.yml. These files would then be available over the TechDocs backend API.
This vulnerability is mitigated by the fact that an attacker would need access to modify the mkdocs.yml in the documentation source code, and would also need access to the TechDocs backend API.
Patches
The vulnerability is patched in the 0.6.3 release of @backstage/techdocs-common.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Backstage repository
- Visit our chat, linked to in Backstage README
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/techdocs-common | all versions | 0.6.3npm install @backstage/techdocs-common@0.6.3 |
Affected Products
backstagelinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/techdocs-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/techdocs-common to 0.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pgf8-28gg-vpr6 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-pgf8-28gg-vpr6 in your dependencies?
Find it across npm, including transitive dependencies.