CVE-2026-106486

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-07) is not newer than that change (2026-10-23), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-94003 (ENISA EUVD) · GHSA-g8rx-f7m5-7794 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Backstage is an open framework for building developer portals. Prior to 0.3.10 in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud and 0.2.25 in @backstage/plugin-scaffolder-backend-module-bitbucket-server, the Bitbucket pull-request Scaffolder actions did not sufficiently validate filesystem paths. An authenticated user who can execute an eligible template and influence an allowed Bitbucket repository could affect paths outside the expected working area, potentially compromising backend confidentiality, integrity, or availability. This issue is fixed in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10 and @backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 23, 2026

Advisory Details (3)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

Improper filesystem validation in Bitbucket pull-request scaffolder actions · Advisory · backstage/backstage · GitHub

https://github.com/backstage/backstage/security/advisories/GHSA-g8rx-f7m5-7794
GitHub release Patch Available

v1.54.6

Patch available: backstage/backstage v1.54.6

https://github.com/backstage/backstage/releases/tag/v1.54.6
GitHub commit Patch Available

commit 818528e112c3 (backstage/backstage)

Patch available: backstage/backstage v1.54.6 (contains commit 818528e112c3)

https://github.com/backstage/backstage/commit/818528e112c36167d76187e9e63fb518399c4dd2

Vendor Advisories for CVE-2026-106486(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@backstage/plugin-scaffolder-backend-module-bitbucket-cloud @ 0.3.10 (fixes < 0.3.10)—ghsa
npm@backstage/plugin-scaffolder-backend-module-bitbucket-server @ 0.2.25 (fixes < 0.2.25)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@backstage/plugin-scaffolder-backend-module-bitbucket-cloud—
  • every version up to 0.3.10: fixed in 0.3.10
—
@backstage/plugin-scaffolder-backend-module-bitbucket-server—
  • every version up to 0.2.25: fixed in 0.2.25
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-13 14:30 UTCEchelonGraph re-scored
  3. 2026-11-13 14:30 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-11-12 14:33 UTCEchelonGraph re-scored
  6. 2026-11-12 14:33 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  7. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-11-11 14:38 UTCEchelonGraph re-scored
  9. 2026-11-11 14:38 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  10. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-11-10 14:43 UTCEchelonGraph re-scored
  12. 2026-11-10 14:43 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  13. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-11-09 14:48 UTCEchelonGraph re-scored
  15. 2026-11-09 14:48 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  16. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-11-08 14:53 UTCEchelonGraph re-scored
  18. 2026-11-08 14:53 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  19. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-11-07 14:58 UTCEchelonGraph re-scored
  21. 2026-11-07 14:58 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  22. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-11-06 15:03 UTCEchelonGraph re-scored
  24. 2026-11-06 15:03 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  25. 2026-11-05 22:25 UTCOSV refresh
Show 66 more
  1. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-11-05 15:08 UTCEchelonGraph re-scored
  3. 2026-11-05 15:08 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  4. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-11-04 15:11 UTCEchelonGraph re-scored
  6. 2026-11-04 15:11 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  7. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-11-03 15:15 UTCEchelonGraph re-scored
  9. 2026-11-03 15:15 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  10. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-11-02 15:19 UTCEchelonGraph re-scored
  12. 2026-11-02 15:19 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  13. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-11-01 15:24 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  15. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-g8rx-f7m5-7794 · GitHub severity HIGH · GitHub CVSS 8.5
  16. 2026-11-01 08:00 UTCEchelonGraph re-scored
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-31 15:30 UTCEchelonGraph re-scored
  19. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-30 15:34 UTCEchelonGraph re-scored
  21. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-29 15:39 UTCEchelonGraph re-scored
  23. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-28 15:29 UTCEchelonGraph re-scored
  25. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-10-27 15:34 UTCEchelonGraph re-scored
  27. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-10-26 15:28 UTCEchelonGraph re-scored
  29. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-10-25 14:54 UTCEchelonGraph re-scored
  31. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-10-24 15:01 UTCEchelonGraph re-scored
  33. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-10-23 15:06 UTCEchelonGraph re-scored▲ 1.40
  35. 2026-10-23 15:05 UTCNVD updateCVSS v3 → 9.9 · severity → CRITICAL
  36. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  39. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  41. 2026-10-18 05:08 UTCEchelonGraph re-scored
  42. 2026-10-17 19:24 UTCEchelonGraph re-scored
  43. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  44. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-10-12 16:39 UTCEchelonGraph re-scored
  49. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-10-11 20:14 UTCEchelonGraph re-scored
  51. 2026-10-11 18:26 UTCEchelonGraph re-scored
  52. 2026-10-11 15:00 UTCEchelonGraph re-scored
  53. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-10-11 00:00 UTCEchelonGraph re-scored
  55. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-10-10 01:35 UTCEchelonGraph re-scored
  57. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-10-09 03:10 UTCEchelonGraph re-scored
  59. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-10-08 04:49 UTCEchelonGraph re-scored
  61. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-10-07 17:39 UTCEchelonGraph re-scored
  63. 2026-10-07 16:44 UTCEchelonGraph re-scored
  64. 2026-10-06 21:32 UTCEchelonGraph re-scored
  65. 2026-10-06 20:37 UTCEchelonGraph re-scoredFirst assessed: 8.5 HIGH
  66. 2026-10-06 20:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-106486?
CVE-2026-106486 is a critical-severity vulnerability; its CVE record was published on October 6, 2026. Backstage is an open framework for building developer portals. Prior to 0.3.10 in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud and 0.2.25 in @backstage/plugin-scaffolder-backend-module-bitbucket-server, the Bitbucket pull-request Scaffolder actions did not sufficiently validate…
When was the CVE record for CVE-2026-106486 published?
The CVE record for CVE-2026-106486 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-106486 actively exploited?
CVE-2026-106486 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106486?
CVE-2026-106486 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-106486?
A fix for CVE-2026-106486 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106486 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-106486

Explore →

Is Your Infrastructure Affected by CVE-2026-106486?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.