CVE-2026-12011

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

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

Use after free in WebMIDI in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVSS v3
8.3
Vendor severity
CRITICALper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Critical)
EG Score
8.3(medium)
EG Risk
42(Track)
EG Risk 42/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 computed
Severity83% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 12, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/518108291
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01962725236.html

Vendor Advisories for CVE-2026-12011(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 149.0.7827.53-1~deb13u1 (369 versions)149.0.7827.114-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (135 versions)149.0.7827.114-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (136 versions)149.0.7827.114-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 326 total refreshes for this CVE.

  1. 2026-09-16 05:14 UTCEPSS rescore
  2. 2026-09-14 04:07 UTCEG score recompute
  3. 2026-09-14 04:07 UTCVendor advisory
  4. 2026-09-14 04:07 UTCGHSA enrichment
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:36 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-30 23:50 UTCEG score recompute
  18. 2026-08-30 23:50 UTCVendor advisory
  19. 2026-08-30 23:50 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:21 UTCEPSS rescore
  22. 2026-08-28 21:40 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-24 23:52 UTCEG score recompute
Show 75 more
  1. 2026-08-24 23:52 UTCVendor advisory
  2. 2026-08-24 23:52 UTCGHSA enrichment
  3. 2026-08-23 23:41 UTCVendor advisory
  4. 2026-08-23 23:41 UTCGHSA enrichment
  5. 2026-08-23 10:39 UTCEG score recompute
  6. 2026-08-23 10:39 UTCVendor advisory
  7. 2026-08-23 10:39 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 01:05 UTCEG score recompute
  10. 2026-08-22 01:05 UTCVendor advisory
  11. 2026-08-22 01:05 UTCGHSA enrichment
  12. 2026-08-21 23:48 UTCEPSS rescore
  13. 2026-08-21 12:02 UTCEG score recompute
  14. 2026-08-21 12:02 UTCVendor advisory
  15. 2026-08-21 12:01 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 21:52 UTCVendor advisory
  18. 2026-08-20 21:52 UTCGHSA enrichment
  19. 2026-08-20 08:50 UTCEG score recompute
  20. 2026-08-20 08:50 UTCVendor advisory
  21. 2026-08-20 08:50 UTCGHSA enrichment
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-19 13:47 UTCEG score recompute
  24. 2026-08-19 13:47 UTCVendor advisory
  25. 2026-08-19 13:47 UTCGHSA enrichment
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 12:31 UTCVendor advisory
  28. 2026-08-17 12:30 UTCGHSA enrichment
  29. 2026-08-16 23:01 UTCEG score recompute
  30. 2026-08-16 23:01 UTCVendor advisory
  31. 2026-08-16 23:01 UTCGHSA enrichment
  32. 2026-08-16 14:56 UTCEPSS rescore
  33. 2026-08-16 06:53 UTCEG score recompute
  34. 2026-08-16 06:53 UTCVendor advisory
  35. 2026-08-16 06:53 UTCGHSA enrichment
  36. 2026-08-16 02:14 UTCEPSS rescore
  37. 2026-08-15 17:52 UTCVendor advisory
  38. 2026-08-15 17:52 UTCGHSA enrichment
  39. 2026-08-15 04:10 UTCEG score recompute
  40. 2026-08-15 04:10 UTCVendor advisory
  41. 2026-08-15 04:10 UTCGHSA enrichment
  42. 2026-08-15 01:30 UTCEPSS rescore
  43. 2026-08-14 15:07 UTCVendor advisory
  44. 2026-08-14 15:07 UTCGHSA enrichment
  45. 2026-08-14 02:05 UTCEG score recompute
  46. 2026-08-14 02:05 UTCVendor advisory
  47. 2026-08-14 02:05 UTCGHSA enrichment
  48. 2026-08-13 22:00 UTCEPSS rescore
  49. 2026-08-13 13:03 UTCVendor advisory
  50. 2026-08-13 13:03 UTCGHSA enrichment
  51. 2026-08-13 00:01 UTCEG score recompute
  52. 2026-08-13 00:01 UTCGHSA enrichment
  53. 2026-08-12 13:50 UTCEPSS rescore
  54. 2026-08-12 11:00 UTCVendor advisory
  55. 2026-08-12 11:00 UTCGHSA enrichment
  56. 2026-08-11 21:57 UTCEG score recompute
  57. 2026-08-11 21:57 UTCVendor advisory
  58. 2026-08-11 21:57 UTCGHSA enrichment
  59. 2026-08-11 13:42 UTCEPSS rescore
  60. 2026-08-11 08:56 UTCEG score recompute
  61. 2026-08-11 08:56 UTCVendor advisory
  62. 2026-08-11 08:56 UTCGHSA enrichment
  63. 2026-08-10 23:59 UTCEPSS rescore
  64. 2026-08-10 19:54 UTCGHSA enrichment
  65. 2026-08-10 04:13 UTCGHSA enrichment
  66. 2026-08-09 15:11 UTCEG score recompute
  67. 2026-08-09 15:11 UTCGHSA enrichment
  68. 2026-08-09 13:46 UTCEPSS rescore
  69. 2026-08-09 02:10 UTCEG score recompute
  70. 2026-08-09 02:10 UTCVendor advisory
  71. 2026-08-09 02:10 UTCGHSA enrichment
  72. 2026-08-08 16:37 UTCEPSS rescore
  73. 2026-08-08 13:08 UTCVendor advisory
  74. 2026-08-08 13:08 UTCGHSA enrichment
  75. 2026-08-08 00:06 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-12011?
CVE-2026-12011 is a high vulnerability published on June 11, 2026. Use after free in WebMIDI in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
When was CVE-2026-12011 disclosed?
CVE-2026-12011 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-12011 actively exploited?
CVE-2026-12011 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 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-12011?
CVE-2026-12011 has a CVSS v3.1 base score of 8.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12011, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12011

Explore →

Is Your Infrastructure Affected by CVE-2026-12011?

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

Start Free Scan →Browse All CVEs