CVE-2026-12016

HIGHPre-NVD 8.38.3
EchelonGraph scoreHIGH 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.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

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

Inappropriate implementation in DevTools in Google Chrome 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: High)

CVSS v3
8.3
EG Score
8.3(high)
EPSS
13.7%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

Vendor Advisories for CVE-2026-12016(2)

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 47× in last 7d / 168× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12016?
CVE-2026-12016 is a high vulnerability published on June 11, 2026. Inappropriate implementation in DevTools in Google Chrome 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: High)
When was CVE-2026-12016 disclosed?
CVE-2026-12016 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12016 actively exploited?
CVE-2026-12016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12016?
CVE-2026-12016 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-12016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12016, 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-12016

Explore →

Is Your Infrastructure Affected by CVE-2026-12016?

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