How severe is GHSA-2g8g-63j4-9w3r?

No CVSS score has been assigned to GHSA-2g8g-63j4-9w3r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2g8g-63j4-9w3r?

GHSA-2g8g-63j4-9w3r affects the following packages: @backstage/plugin-scaffolder-backend (npm). Ecosystems affected: npm.

How do I fix GHSA-2g8g-63j4-9w3r?

Update @backstage/plugin-scaffolder-backend to 0.15.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g8g-63j4-9w3r is resolved across your whole dependency graph.

How do I detect GHSA-2g8g-63j4-9w3r in my npm dependencies?

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.

How do I mitigate GHSA-2g8g-63j4-9w3r if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-2g8g-63j4-9w3r?

O3 pinpoints whether GHSA-2g8g-63j4-9w3r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2g8g-63j4-9w3r actively exploited in the wild?

No public exploit code has been indexed for GHSA-2g8g-63j4-9w3r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2g8g-63j4-9w3r published, and has it been updated?

GHSA-2g8g-63j4-9w3r was published on December 1, 2021 and was last updated on November 29, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-2g8g-63j4-9w3r: @backstage/plugin-scaffol… Remote Code Exe…

Blast Radius

1 pkg affected

📦@backstage/plugin-scaffolder-backend

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

The templating library used by the scaffolder backend assumes that templates are trusted which is an undesired property of the scaffolder-backend. This has now been mitigated by sandboxing the template code execution.

Impact

A malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template yaml definition itself and not by user input data.

Patches

This is vulnerability is patched in version 0.15.14 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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-scaffolder-backend`	all versions	0.15.14

Detection & mitigation playbook

Open-source dependency

Detect
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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g8g-63j4-9w3r 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-2g8g-63j4-9w3r 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-2g8g-63j4-9w3r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The templating library used by the scaffolder backend assumes that templates are trusted which is an undesired property of the scaffolder-backend. This has now been mitigated by sandboxing the template code execution. ### Impact A malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template yaml definition itself and not by user input data. ### Patches This is vulnerability is patched in version `0.15.14` of `@backstage/plugin-sca

O3 Security · Impact-Aware SCA

Is GHSA-2g8g-63j4-9w3r in your dependencies?

O3 detects GHSA-2g8g-63j4-9w3r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works