CVE-2026-106460

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreHIGH confidence

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

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2026-10-07. A secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-93995 (ENISA EUVD) · GHSA-xm5q-p7w3-x6cp (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Backstage is an open framework for building developer portals. From 0.3.0 until 0.6.15 and 0.7.5, the @backstage/plugin-auth-node package did not consistently honor explicit negative email verification during shared OAuth profile normalization. The affected paths include a selected profile email marked verified: false, a matching raw provider email marked email_verified: false, and an email obtained only from an ID token marked email_verified: false. Exploitation requires an admitted identity-provider user who can supply or change an unverified email and a deployment that uses the selected profile email to resolve catalog identities. The verification metadata must apply to the selected email; an absent email_verified claim alone is not affected. In an affected configuration, the user may assume another catalog identity and obtain its associated access and permissions. This issue is fixed in versions 0.6.15 and 0.7.5.

CVSS v3
6.8
EG Score
6.8MEDIUMhigh confidence
EG Risk
31
EG Risk 31/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)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
24th
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 (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 27, 2026

Advisory Details (6)

Auto-updated Oct 6, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v1.54.7

Patch available: backstage/backstage v1.54.7

https://github.com/backstage/backstage/releases/tag/v1.54.7
GitHub release Patch Available

v1.49.7

Patch available: backstage/backstage v1.49.7

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

commit fc5e30aba8ea (backstage/backstage)

Patch available: backstage/backstage v1.54.7 (contains commit fc5e30aba8ea)

https://github.com/backstage/backstage/commit/fc5e30aba8ea7282ed3658c3b985cec71051cf9d
GitHub commit Patch Available

commit f0a43dacd1b5 (backstage/backstage)

Patch available: backstage/backstage v1.49.7 (contains commit f0a43dacd1b5)

https://github.com/backstage/backstage/commit/f0a43dacd1b501064da042b43eab9c1e06371d38
GitHub commit Patch Available

commit 507e65ab9160 (backstage/backstage)

Patch available: backstage/backstage v1.55.0 (contains commit 507e65ab9160)

https://github.com/backstage/backstage/commit/507e65ab9160aae6b602513dbfaebdd6be0ca8bb
GitHub advisoryMentions a patch (unverified)

Explicit negative email verification can be ignored during shared OAuth profile normalization · Advisory · backstage/backstage · GitHub

https://github.com/backstage/backstage/security/advisories/GHSA-xm5q-p7w3-x6cp

Vendor Advisories for CVE-2026-106460(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-auth-node @ 0.6.15 (fixes >= 0.3.0, < 0.6.15)—ghsa
npm@backstage/plugin-auth-node @ 0.7.5 (fixes >= 0.7.0, < 0.7.5)—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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@backstage/plugin-auth-node—
  • 0.3.0 up to 0.6.15: fixed in 0.6.15
  • 0.7.0 up to 0.7.5: fixed in 0.7.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-xm5q-p7w3-x6cp · GitHub severity MODERATE · GitHub CVSS 6.8
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-27 20:50 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-25 14:54 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-10-23 08:48 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-18 05:08 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 18 more
  1. 2026-10-12 16:39 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-11 20:14 UTCEG score recompute
  4. 2026-10-11 18:27 UTCEG score recompute
  5. 2026-10-11 15:00 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-11 04:05 UTCEG score recompute
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-10 03:12 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-09 02:18 UTCEG score recompute
  12. 2026-10-09 01:59 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-08 15:14 UTCEG score recompute
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-06 21:32 UTCEG score recompute
  17. 2026-10-06 20:37 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  18. 2026-10-06 20:36 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-106460?
CVE-2026-106460 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Backstage is an open framework for building developer portals. From 0.3.0 until 0.6.15 and 0.7.5, the @backstage/plugin-auth-node package did not consistently honor explicit negative email verification during shared OAuth profile normalization. The affected paths include a selected profile email…
When was the CVE record for CVE-2026-106460 published?
The CVE record for CVE-2026-106460 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 27, 2026; the record at its source may have been updated since.
Is CVE-2026-106460 actively exploited?
CVE-2026-106460 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106460?
CVE-2026-106460 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106460?
A fix for CVE-2026-106460 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106460 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-106460

Explore →

Is Your Infrastructure Affected by CVE-2026-106460?

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

Book a Demo →Browse All CVEs