CVE-2026-19162

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. 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.

Out of bounds write in V8 in Google Chrome prior to 151.0.7922.109 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(high)
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
37%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-19162(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 (503 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 151.0.7922.71-1~deb13u1 (400 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (163 versions)151.0.7922.108-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (165 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 78× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:08 UTCVendor advisory
  3. 2026-08-20 21:08 UTCGHSA enrichment
  4. 2026-08-20 07:58 UTCVendor advisory
  5. 2026-08-20 07:58 UTCGHSA enrichment
  6. 2026-08-19 18:49 UTCEG score recompute
  7. 2026-08-19 18:49 UTCVendor advisory
  8. 2026-08-19 18:48 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 04:50 UTCVendor advisory
  11. 2026-08-19 04:50 UTCGHSA enrichment
  12. 2026-08-18 15:41 UTCEG score recompute
  13. 2026-08-18 15:41 UTCVendor advisory
  14. 2026-08-18 15:41 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 01:18 UTCEG score recompute
  17. 2026-08-18 01:18 UTCVendor advisory
  18. 2026-08-18 01:18 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 12:02 UTCVendor advisory
  21. 2026-08-17 12:02 UTCGHSA enrichment
  22. 2026-08-16 22:52 UTCEG score recompute
  23. 2026-08-16 22:52 UTCVendor advisory
  24. 2026-08-16 22:52 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 53 more
  1. 2026-08-16 09:43 UTCEG score recompute
  2. 2026-08-16 09:43 UTCVendor advisory
  3. 2026-08-16 09:43 UTCGHSA enrichment
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 20:34 UTCVendor advisory
  6. 2026-08-15 20:34 UTCGHSA enrichment
  7. 2026-08-15 07:24 UTCEG score recompute
  8. 2026-08-15 07:24 UTCVendor advisory
  9. 2026-08-15 07:24 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 18:14 UTCVendor advisory
  12. 2026-08-14 18:14 UTCGHSA enrichment
  13. 2026-08-14 05:05 UTCEG score recompute
  14. 2026-08-14 05:05 UTCVendor advisory
  15. 2026-08-14 05:05 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 15:55 UTCVendor advisory
  18. 2026-08-13 15:55 UTCGHSA enrichment
  19. 2026-08-13 02:46 UTCEG score recompute
  20. 2026-08-13 02:46 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-12 13:36 UTCVendor advisory
  23. 2026-08-12 13:36 UTCGHSA enrichment
  24. 2026-08-12 00:26 UTCEG score recompute
  25. 2026-08-12 00:26 UTCVendor advisory
  26. 2026-08-12 00:26 UTCGHSA enrichment
  27. 2026-08-11 13:42 UTCEPSS rescore
  28. 2026-08-11 11:17 UTCEG score recompute
  29. 2026-08-11 11:17 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 22:08 UTCGHSA enrichment
  32. 2026-08-10 08:58 UTCGHSA enrichment
  33. 2026-08-09 19:49 UTCEG score recompute
  34. 2026-08-09 19:49 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 06:40 UTCGHSA enrichment
  37. 2026-08-08 17:31 UTCEG score recompute
  38. 2026-08-08 17:31 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 04:21 UTCEG score recompute
  41. 2026-08-08 04:21 UTCGHSA enrichment
  42. 2026-08-07 15:11 UTCGHSA enrichment
  43. 2026-08-07 13:51 UTCGHSA enrichment
  44. 2026-08-07 05:19 UTCGHSA enrichment
  45. 2026-08-07 04:18 UTCEG score recompute
  46. 2026-08-07 04:18 UTCGHSA enrichment
  47. 2026-08-07 02:17 UTCGHSA enrichment
  48. 2026-08-07 01:29 UTCEG score recompute
  49. 2026-08-07 01:29 UTCGHSA enrichment
  50. 2026-08-07 01:28 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  51. 2026-08-06 22:18 UTCEG score recompute
  52. 2026-08-06 22:18 UTCNVD update
  53. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19162?

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