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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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.

📦 npm

Not in CISA KEV

RCE vulnerability affecting v1beta3 templates in @backstage/plugin-scaffolder-backendGHSA-2g8g-63j4-9w3r

GHSA-2g8g-63j4-9w3r is a remote code execution vulnerability in @backstage/plugin-scaffolder-backend. A fix is available for @backstage/plugin-scaffolder-backend — see the affected versions and patch details below.

Published

Dec 1, 2021

Updated

Nov 29, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

69other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@backstage/plugin-scaffolder-backendnpm

107Kdownloads / week

Description

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`npm install @backstage/plugin-scaffolder-backend@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works