Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Backstage has improper input validation in scaffolder task list orderingGHSA-vwp5-f99x-x3rq

MEDIUMFix: backstage/backstage@e673a86

GHSA-vwp5-f99x-x3rq is a medium-severity (CVSS 5.3) CWE-202 vulnerability in @backstage/plugin-scaffolder-backend. A fix is available for @backstage/plugin-scaffolder-backend — see the affected versions and patch details below.

Also known asCVE-2026-106506
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-vwp5-f99x-x3rq.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-vwp5-f99x-x3rq 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

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
68Kdownloads / week

Description

Impact

An authenticated Backstage user with permission to create and read relevant scaffolder tasks may be able to infer confidential task data under specific conditions. Successful exploitation requires retained task secrets, visibility of a target task, knowledge of the secret structure, and repeated requests.

Patches

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

Workarounds

  • At the gateway or reverse proxy, reject task-list requests that specify custom ordering, or allow ordering only by created_at, status, and created_by.
  • Restrict scaffolder task creation and task read permissions to trusted users, preferably using owner-based task-read conditions.
  • Disabling task recovery can reduce secret retention after a task is claimed, but it does not protect secrets in queued tasks and should not be treated as complete mitigation.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@backstage/plugin-scaffolder-backendall versions4.1.0npm install @backstage/plugin-scaffolder-backend@4.1.0

Affected Products

2 products · 2 configurations
Application
backstagelinuxfoundation
< 1.54.6
range
Application
backstage\/plugin-scaffolder-backendlinuxfoundation
< 4.1.0
range

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. 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-vwp5-f99x-x3rq is resolved across your whole dependency graph.

  3. 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.

Red HatModerate

This vulnerability is rated as having Moderate impact because exploitation requires an authenticated account with existing permissions to create and view scaffolder tasks, high attack complexity, and repeated requests to infer sensitive task parameters. In environments deploying Red Hat Developer Hub or Ansible…

Workaround published by Red Hat
To mitigate this configure your reverse proxy or gateway to reject task-list requests with custom ordering, or strictly limit them to safe fields like created_at, status, and created_by. Enforce strict role-based access controls to restrict scaffolder task creation and read permissions exclusively to trusted users, preferably via owner-based conditions. Additionally, disable task recovery to reduce secret retention for claimed tasks and minimize the overall window of potential exposure.
Source: Red Hat security advisory for GHSA-vwp5-f99x-x3rq (CC BY 4.0)

Frequently Asked Questions

### Impact An authenticated Backstage user with permission to create and read relevant scaffolder tasks may be able to infer confidential task data under specific conditions. Successful exploitation requires retained task secrets, visibility of a target task, knowledge of the secret structure, and repeated requests. ### Patches Patched in `@backstage/plugin-scaffolder-backend` version `4.1.0` ### Workarounds - At the gateway or reverse proxy, reject task-list requests that specify custom ordering, or allow ordering only by `created_at`, `status`, and `created_by`. - Restrict scaffolder ta
O3 Security · Impact-Aware SCA

Is GHSA-vwp5-f99x-x3rq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Backstage has improper input validation in scaffolder task…