CVE-2026-11218

HIGHPre-NVD 6.88.1▲
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.8; sources differ by 1.3.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

Inappropriate implementation in PlatformIntegration in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a malicious file. (Chromium security severity: Low)

CVSS v3
6.8
Vendor severity
LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 23, 2026

Advisory Details (2)

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

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-11218(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 ... 148.0.7778.96-3 (363 versions)149.0.7827.53-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions)149.0.7827.53-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (130 versions)149.0.7827.53-1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 315 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11218?
CVE-2026-11218 is a high vulnerability published on June 4, 2026. Inappropriate implementation in PlatformIntegration in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a malicious file. (Chromium security severity: Low)
When was CVE-2026-11218 disclosed?
CVE-2026-11218 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 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-11218 actively exploited?
CVE-2026-11218 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 89.9% of all scored CVEs.
What is the CVSS score of CVE-2026-11218?
CVE-2026-11218 has a CVSS v3.1 base score of 6.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2026-11218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11218, 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-11218

Explore →

Is Your Infrastructure Affected by CVE-2026-11218?

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

Start Free Scan →Browse All CVEs