CVE-2026-9918

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-29. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: None knownExposed: 0

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

Inappropriate implementation in Tint in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

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

Published

May 28, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated Aug 30, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-9918(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 (359 versions)148.0.7778.215-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (125 versions)148.0.7778.215-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (126 versions)148.0.7778.215-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 204× 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 566 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9918?
CVE-2026-9918 is a critical vulnerability published on May 28, 2026. Inappropriate implementation in Tint in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-9918 disclosed?
CVE-2026-9918 was first published in the National Vulnerability Database on May 28, 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-9918 actively exploited?
CVE-2026-9918 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 84.6% of all scored CVEs.
What is the CVSS score of CVE-2026-9918?
CVE-2026-9918 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-9918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9918, 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-9918

Explore →

Is Your Infrastructure Affected by CVE-2026-9918?

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

Start Free Scan →Browse All CVEs