Backstage may expose sensitive information in Scaffolder task failure eventsGHSA-95p4-vv4g-jxxm
MEDIUMFix: backstage/backstage@3f1e869GHSA-95p4-vv4g-jxxm is a medium-severity (CVSS 5.3) CWE-532 vulnerability in @backstage/plugin-scaffolder-backend. A fix is available for @backstage/plugin-scaffolder-backend — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-95p4-vv4g-jxxm.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-95p4-vv4g-jxxm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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/plugin-scaffolder-backendnpmDescription
Impact
Under specific template and failure conditions, an authenticated user may be able to retrieve sensitive values from Scaffolder task events. This can expose backend-managed credentials used during task execution.
Patches
Patched in @backstage/plugin-scaffolder-backend version 4.1.0
Workarounds
- Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/plugin-scaffolder-backend | all versions | 4.1.0npm install @backstage/plugin-scaffolder-backend@4.1.0 |
Affected Products
backstagelinuxfoundationbackstage\/plugin-scaffolder-backendlinuxfoundationDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-scaffolder-backend to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95p4-vv4g-jxxm 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as Moderate for Red Hat products because exploitation requires valid authentication and relies on high attack complexity, specifically the failure of particular Scaffolder templates. In deployments of Red Hat Developer Hub and Ansible Automation Platform, backend-managed secrets could be…
To mitigate this strictly limit Scaffolder template execution and task-event log access to highly trusted administrators, preventing unauthorized users from viewing sensitive failure events. Additionally, proactively identify, revoke, and rotate any backend-managed secrets or credentials that may have already leaked into historical task failure logs.Source: Red Hat security advisory for GHSA-95p4-vv4g-jxxm (CC BY 4.0)
Frequently Asked Questions
Is GHSA-95p4-vv4g-jxxm in your dependencies?
Find it across npm, including transitive dependencies.