CVE-2026-12018

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH 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
Trending — 4 sources updated this week
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.

Inappropriate implementation in Mojo in Google Chrome on Windows prior to 149.0.7827.115 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)

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

Frequently asked(5)

What is CVE-2026-12018?
CVE-2026-12018 is a high vulnerability published on June 11, 2026. Inappropriate implementation in Mojo in Google Chrome on Windows prior to 149.0.7827.115 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)
When was CVE-2026-12018 disclosed?
CVE-2026-12018 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-12018 actively exploited?
CVE-2026-12018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12018?
CVE-2026-12018 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-12018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12018, 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-12018

Explore →

Is Your Infrastructure Affected by CVE-2026-12018?

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