CVE-2026-106487

MEDIUMNVD 5.05.0
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.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-22), so it does not.

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

Also known asEUVD-2026-94005 (ENISA EUVD) · GHSA-h53x-hjx6-25gr (GitHub Security Advisories)Source: ENISA EUVD

5.0EG
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: 5.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Backstage is an open framework for building developer portals. Prior to 0.21.10, the @backstage/plugin-kubernetes-backend package is affected by unsupported catalog cluster authentication mode in kubernetes backend. Deployments using catalog cluster discovery may be affected when catalog contributors can create or modify kubernetes-cluster Resource entities. With the required endpoint permissions and pod RBAC, the backend can use its local in-cluster identity, potentially exposing Kubernetes resources readable by that identity. The credential is used only with the local in-cluster API endpoint and is not sent to the catalog-supplied endpoint. This issue is fixed in version 0.21.10.

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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)
Severity50% × 45%
Impact severity (EG Severity): CVSS 5.0 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
18th
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 (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.

EG Severity
5.0 MEDIUMCVSS-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.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 every mission impact level.CISA BOD 26-04: 60 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 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). 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)60 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 partial (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 22, 2026

Advisory Details (3)

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

Unsupported catalog cluster authentication mode in kubernetes backend · Advisory · backstage/backstage · GitHub

https://github.com/backstage/backstage/security/advisories/GHSA-h53x-hjx6-25gr
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 c14f8be6908f (backstage/backstage)

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

https://github.com/backstage/backstage/commit/c14f8be6908f0f719b16356e5492352311e28946

Vendor Advisories for CVE-2026-106487(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@backstage/plugin-kubernetes-backend @ 0.21.10 (fixes < 0.21.10)—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-kubernetes-backend—
  • every version up to 0.21.10: fixed in 0.21.10
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 32× 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.3% · 18th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-h53x-hjx6-25gr · GitHub severity LOW · GitHub CVSS 3.5
  14. 2026-11-01 08:00 UTCEchelonGraph re-scored
  15. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-30 06:55 UTCOSV refresh
  18. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-10-25 14:54 UTCEchelonGraph re-scored
  24. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 28 more
  1. 2026-10-22 19:08 UTCEchelonGraph re-scored▲ 1.50
  2. 2026-10-22 19:05 UTCNVD updateCVSS v3 → 5 · severity → MEDIUM
  3. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-18 05:08 UTCEchelonGraph re-scored
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-12 16:39 UTCEchelonGraph re-scored
  15. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-11 20:14 UTCEchelonGraph re-scored
  17. 2026-10-11 18:26 UTCEchelonGraph re-scored
  18. 2026-10-11 15:00 UTCEchelonGraph re-scored
  19. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-09 02:18 UTCEchelonGraph re-scored
  23. 2026-10-09 01:58 UTCEchelonGraph re-scored
  24. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-10-06 21:32 UTCEchelonGraph re-scored
  27. 2026-10-06 20:53 UTCEchelonGraph re-scoredFirst assessed: 3.5 LOW
  28. 2026-10-06 20:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

npm:@backstage/plugin-kubernetes-backend

Frequently asked(5)

What is CVE-2026-106487?
CVE-2026-106487 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Backstage is an open framework for building developer portals. Prior to 0.21.10, the @backstage/plugin-kubernetes-backend package is affected by unsupported catalog cluster authentication mode in kubernetes backend. Deployments using catalog cluster discovery may be affected when catalog…
When was the CVE record for CVE-2026-106487 published?
The CVE record for CVE-2026-106487 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-106487 actively exploited?
CVE-2026-106487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106487?
CVE-2026-106487 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-106487?
A fix for CVE-2026-106487 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106487 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-106487

Explore →

Is Your Infrastructure Affected by CVE-2026-106487?

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

Book a Demo →Browse All CVEs