CVE-2026-16418

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Stack buffer overflow in V8 in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (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.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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-16418(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 ... 150.0.7871.46-1~deb13u1 (390 versions)150.0.7871.181-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (156 versions)150.0.7871.181-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (157 versions)150.0.7871.181-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 120× 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 569 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-16418?
CVE-2026-16418 is a high vulnerability published on July 21, 2026. Stack buffer overflow in V8 in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-16418 disclosed?
CVE-2026-16418 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16418 actively exploited?
CVE-2026-16418 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16418?
CVE-2026-16418 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-16418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16418, 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-16418

Explore →

Is Your Infrastructure Affected by CVE-2026-16418?

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