Backstage is an open framework for building developer portals. From 0.3.0 until 0.3.8, the @backstage/plugin-scaffolder-backend-module-sentry package is affected by improper input validation in sentry scaffolder actions. An authenticated internal user who can execute the affected actions may cause the backend to contact unintended destinations and disclose Sentry integration credentials. Subsequent impact depends on network reachability and the privileges granted to the configured token. This issue is fixed in version 0.3.8.
CVE-2026-106459
This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.5
- EG Score
- 8.5HIGHlow confidence
- EG Risk
- 38EG Risk 38/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (4)
Auto-updated Oct 6, 2026v1.55.0
Patch available: backstage/backstage v1.55.0
https://github.com/backstage/backstage/releases/tag/v1.55.0v1.54.8
Patch available: backstage/backstage v1.54.8
https://github.com/backstage/backstage/releases/tag/v1.54.8commit b0170fad7962 (backstage/backstage)
Patch available: backstage/backstage v1.54.8 (contains commit b0170fad7962)
https://github.com/backstage/backstage/commit/b0170fad7962fb8c3d71366b5265cf283c7bbcf7Improper input validation in Sentry scaffolder actions · Advisory · backstage/backstage · GitHub
https://github.com/backstage/backstage/security/advisories/GHSA-g734-fhp4-7mfpVendor Advisories for CVE-2026-106459(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 17:39 UTCEG score recompute
- 2026-10-07 16:44 UTCEG score recompute
- 2026-10-06 21:32 UTCEG score recompute
- 2026-10-06 20:22 UTCEG score recompute
- 2026-10-06 20:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-106459?
When was CVE-2026-106459 disclosed?
What is the CVSS score of CVE-2026-106459?
How do I remediate CVE-2026-106459?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-106459
Is Your Infrastructure Affected by CVE-2026-106459?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.