GHSA-hmp2-4m7g-22cv: High severity npm/@backstage/plugin-scaffolder-backend vulnerability

Published Oct 7, 2026
·
Updated

Impact

An authenticated user with access to affected Scaffolder templates could bypass configured action restrictions. Depending on integration credentials, this could grant unauthorized access to repositories and related source-control resources.

Patches

Patched in @backstage/plugin-scaffolder-backend version 4.1.0

Workarounds

- Restrict affected Scaffolder actions to trusted users and configure source-control integrations with least-privilege credentials.

Affected Software

4 affected componentsFixes available
npm/@backstage/plugin-scaffolder-backend>=4.0.4<4.1.0
4.1.0
npm/@backstage/plugin-scaffolder-backend>=4.0.0<4.0.3
4.0.3
npm/@backstage/plugin-scaffolder-backend>=3.4.0<3.4.1
3.4.1
npm/@backstage/plugin-scaffolder-backend<3.3.1
3.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@backstage/plugin-scaffolder-backend to a version that resolves this vulnerability.

    Fixed in 4.1.0
  2. Upgrade

    Upgrade npm/@backstage/plugin-scaffolder-backend to a version that resolves this vulnerability.

    Fixed in 4.0.3
  3. Upgrade

    Upgrade npm/@backstage/plugin-scaffolder-backend to a version that resolves this vulnerability.

    Fixed in 3.4.1
  4. Upgrade

    Upgrade npm/@backstage/plugin-scaffolder-backend to a version that resolves this vulnerability.

    Fixed in 3.3.1
  5. Upgrade

    Upgrade @backstage/plugin-scaffolder-backend to a version that resolves this vulnerability.

    Fixed in 4.1.0
  6. Compensating control

    Restrict affected Scaffolder actions to trusted users and configure source-control integrations with least-privilege credentials.

Event History

Oct 7, 2026
Advisory Published
via GitHub·05:59 PM
Data Sourced
via GitHub·05:59 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Organizations using affected Scaffolder templates where authenticated users can access template actions are exposed. The impact depends on the permissions of configured source-control integration credentials.

2

What does an attacker need to exploit it?

An attacker needs to be an authenticated user with access to affected Scaffolder templates. No user interaction is required.

3

What should be done if upgrading is not immediately possible?

Restrict access to affected Scaffolder actions to trusted users. Configure source-control integrations with least-privilege credentials to limit repository and related source-control access if restrictions are bypassed.

4

What version contains the fix?

The issue is patched in @backstage/plugin-scaffolder-backend version 4.1.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203