Uninitialized resource in Skia in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
CVE-2026-78958
MEDIUMCVSS · not yet scored6.5Trending — 5 sources updated this week
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.3% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 6.5(low)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
References (2)
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html
- chrome-cve-admin@googlehttps://issues.chromium.org/issues/497205529
Vendor Advisories for CVE-2026-78958(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-08-26 16:42 UTCEG score recompute
- 2026-08-26 16:42 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 21:33 UTCGHSA enrichment
- 2026-08-25 21:25 UTCNVD update
- 2026-08-25 20:31 UTCEG score recompute
- 2026-08-25 20:25 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-78958?
CVE-2026-78958 is a medium vulnerability published on August 25, 2026. Uninitialized resource in Skia in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-78958 disclosed?
CVE-2026-78958 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78958 actively exploited?
CVE-2026-78958 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.7% of all scored CVEs.
How do I remediate CVE-2026-78958?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78958, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78958
Is Your Infrastructure Affected by CVE-2026-78958?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.