CVE-2026-103627

MEDIUMCVSS · not yet scored6.5
EchelonGraph scoreLOW confidence

Google's Chromium security team rated this Medium in the advisory text — the exact wording is "(Chromium security severity: Medium)". Chromium's CNA does not publish a CVSS vector, and NVD has not yet analysed this record, so there is no CVSS v3.1, v4.0 or v2.0 base score for it from any source. EchelonGraph publishes 6.5 (MEDIUM), derived from the VENDOR'S OWN SEVERITY BAND — not from a CVSS vector. That number is calibrated, not assumed: across 859 Chromium CVEs that NVD has since scored, a Chromium "Medium" carried a median CVSS v3 base of 6.5. This score is provisional and will be superseded the moment any source publishes a real CVSS base. EPSS predicts 0.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift a vendor-band score. Confidence: LOW.

Sources: epss, vendor_prose:chromium
Trending — 5 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Information leak in SVG in Google Chrome prior to 154.0.8037.97 allowed a remote attacker to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
—
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
6.5MEDIUMlow confidence
EG Risk
29
EG Risk 29/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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 2, 2026

Last Modified

October 3, 2026

Vendor Advisories for CVE-2026-103627(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 154.0.8037.92-1~deb13u1 (431 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 154.0.8037.92-1~deb13u1 (196 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 154.0.8037.92-1~deb13u1 (196 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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.

  1. 2026-10-05 06:44 UTCGHSA enrichment
  2. 2026-10-04 23:21 UTCEPSS rescore
  3. 2026-10-04 05:31 UTCEG score recompute
  4. 2026-10-04 05:31 UTCGHSA enrichment
  5. 2026-10-03 14:25 UTCEPSS rescore
  6. 2026-10-03 04:20 UTCGHSA enrichment
  7. 2026-10-03 04:19 UTCNVD update
  8. 2026-10-03 04:00 UTCEG score recompute
  9. 2026-10-03 04:00 UTCGHSA enrichment
  10. 2026-10-03 03:59 UTCMITRE cvelistV5
  11. 2026-10-02 16:25 UTCNVD update
  12. 2026-10-02 16:13 UTCEG score recompute
  13. 2026-10-02 16:11 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-103627?
CVE-2026-103627 is a medium vulnerability published on October 2, 2026. Information leak in SVG in Google Chrome prior to 154.0.8037.97 allowed a remote attacker to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-103627 disclosed?
CVE-2026-103627 was first published on October 2, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103627 actively exploited?
CVE-2026-103627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-103627?
No fix for CVE-2026-103627 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-103627 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-103627

Explore →

Is Your Infrastructure Affected by CVE-2026-103627?

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