GHSA-pvv8-8fx9-h673 is a medium-severity (CVSS 6.8) Path Traversal vulnerability in @backstage/plugin-scaffolder-backend. O3 Security confirms whether GHSA-pvv8-8fx9-h673 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Path Traversal in @backstage/plugin-scaffolder-backend
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@backstage/plugin-scaffolder-backendnpmDescription
Impact
A malicious actor could read sensitive files from the environment where Scaffolder tasks are run. The attack is executed by crafting a custom Scaffolder template with a publish:github:pull-request action using a particular source path. When the template is executed the sensitive files would be included in the published pull request.
This vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request.
Patches
The vulnerability is patched in the 0.15.9 release of @backstage/plugin-scaffolder-backend.
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/plugin-scaffolder-backend | ≥ 0.9.4&&< 0.15.9 | 0.15.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-scaffolder-backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @backstage/plugin-scaffolder-backend to 0.15.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pvv8-8fx9-h673 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pvv8-8fx9-h673 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pvv8-8fx9-h673. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pvv8-8fx9-h673 in your dependencies?
O3 detects GHSA-pvv8-8fx9-h673 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.