CVE-2026-12018

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/516808201
Web page

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-12018(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 rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 149.0.7827.53-1~deb13u1 (369 versions)
  • every version up to 149.0.7827.114-1~deb12u1: fixed in 149.0.7827.114-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (135 versions)
  • every version up to 149.0.7827.114-1~deb13u1: fixed in 149.0.7827.114-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (136 versions)
  • every version up to 149.0.7827.114-1: fixed in 149.0.7827.114-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 358 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 258 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12018?
CVE-2026-12018 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-12018 published?
The CVE record for CVE-2026-12018 was published on June 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 23, 2026; the record at its source may have been updated since.
Is CVE-2026-12018 actively exploited?
CVE-2026-12018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-12018 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12018 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs