CVE-2026-9111

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: 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 WebRTC in Google Chrome on Linux prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

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

Published

May 20, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated May 22, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.html

Vendor Advisories for CVE-2026-9111(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 (356 versions)148.0.7778.178-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (122 versions)148.0.7778.178-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (123 versions)148.0.7778.178-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 82× 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 264 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9111?
CVE-2026-9111 is a high vulnerability published on May 20, 2026. Use after free in WebRTC in Google Chrome on Linux prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)
When was CVE-2026-9111 disclosed?
CVE-2026-9111 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9111 actively exploited?
CVE-2026-9111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.0% of all scored CVEs.
What is the CVSS score of CVE-2026-9111?
CVE-2026-9111 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-9111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9111, 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-9111

Explore →

Is Your Infrastructure Affected by CVE-2026-9111?

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

Start Free Scan →Browse All CVEs