CVE-2026-106493

MEDIUMNVD 4.14.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.0 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
Trending — 4 sources updated this week

Also known asEUVD-2026-94013 (ENISA EUVD) · GHSA-xvh9-35w9-42m4 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

Backstage is an open framework for building developer portals. Prior to 1.54.6, cloud storage catalog providers did not sufficiently validate object paths. A principal able to create or rename objects in a configured Azure Blob Storage or AWS S3 catalog source could cause catalog descriptors to be read from outside the intended storage boundary, limited to locations reachable with the backend's configured credentials. This issue is fixed in 1.54.6.

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity41% × 45%
Impact severity (EG Severity): CVSS 4.1 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
20th
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 (4.1): severity, escalated by confirmed exploitation. This CVE's 4.1 is its impact severity (EG Severity), not escalated.

EG Severity
4.1 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)

Cloud storage catalog locations may cross configured storage boundaries · Advisory · backstage/backstage · GitHub

https://github.com/backstage/backstage/security/advisories/GHSA-xvh9-35w9-42m4
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 47ddbd8b4a3e (backstage/backstage)

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

https://github.com/backstage/backstage/commit/47ddbd8b4a3efd812309f759c38f4877fbd9e5ff

Vendor Advisories for CVE-2026-106493(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@backstage/backend-defaults @ 0.17.8 (fixes < 0.17.8)—ghsa
npm@backstage/plugin-catalog-backend-module-aws @ 0.4.27 (fixes < 0.4.27)—ghsa
npm@backstage/plugin-catalog-backend-module-azure @ 0.3.21 (fixes < 0.3.21)—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

(3 across 1 ecosystem)
npm(3)
PackageVulnerable rangeFix by version rangeDependents
@backstage/backend-defaults—
  • every version up to 0.17.8: fixed in 0.17.8
—
@backstage/plugin-catalog-backend-module-aws—
  • every version up to 0.4.27: fixed in 0.4.27
—
@backstage/plugin-catalog-backend-module-azure—
  • every version up to 0.3.21: fixed in 0.3.21
—

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% · 20th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-xvh9-35w9-42m4 · GitHub severity LOW · GitHub CVSS 3.0
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-30 00:55 UTCOSV refresh
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-25 14:54 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-22 13:28 UTCEG score recompute▲ 1.10
  17. 2026-10-22 13:25 UTCNVD updateCVSS v3 → 4.1 · severity → MEDIUM
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-18 05:08 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 18 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-12 16:39 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-11 20:14 UTCEG score recompute
  6. 2026-10-11 18:26 UTCEG score recompute
  7. 2026-10-11 15:00 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-10 19:35 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-07 19:19 UTCEG score recompute
  15. 2026-10-07 18:28 UTCEG score recompute
  16. 2026-10-06 21:32 UTCEG score recompute
  17. 2026-10-06 20:58 UTCEG score recomputeFirst assessed: 3.0 LOW
  18. 2026-10-06 20:56 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-106493?
CVE-2026-106493 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 1.54.6, cloud storage catalog providers did not sufficiently validate object paths. A principal able to create or rename objects in a configured Azure Blob Storage or AWS S3 catalog source could cause catalog descriptors to be…
When was the CVE record for CVE-2026-106493 published?
The CVE record for CVE-2026-106493 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-106493 actively exploited?
CVE-2026-106493 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106493?
CVE-2026-106493 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2026-106493?
A fix for CVE-2026-106493 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106493 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-106493

Explore →

Is Your Infrastructure Affected by CVE-2026-106493?

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

Book a Demo →Browse All CVEs