Use after free in Media in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-12013 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
Determined not a vulnerability
CVE-2026-12013
✕ Withdrawn — historical dataHIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 14.9%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
June 12, 2026
Advisory Details (2)
Auto-updated Jun 12, 2026No patch confirmed yet.
generic
Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01962725236.htmlVendor Advisories for CVE-2026-12013(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(5)
What is CVE-2026-12013?
CVE-2026-12013 is a high vulnerability published on June 11, 2026. Use after free in Media in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-12013 disclosed?
CVE-2026-12013 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12013 actively exploited?
CVE-2026-12013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12013?
CVE-2026-12013 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12013, 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-12013
Is Your Infrastructure Affected by CVE-2026-12013?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.