CVE-2026-8519

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. 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: 0.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer overflow in ANGLE in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to perform an out of bounds memory write 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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

Published

May 14, 2026

Last Modified

May 19, 2026

Advisory Details (2)

Auto-updated May 14, 2026
Patch available.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-8519(3)

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 rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 148.0.7778.96-3 (353 versions)
  • every version up to 148.0.7778.167-1~deb12u1: fixed in 148.0.7778.167-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (119 versions)
  • every version up to 148.0.7778.167-1~deb13u1: fixed in 148.0.7778.167-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (120 versions)
  • every version up to 148.0.7778.167-1: fixed in 148.0.7778.167-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8519?
CVE-2026-8519 is a high vulnerability published on May 14, 2026. Integer overflow in ANGLE in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
When was CVE-2026-8519 disclosed?
CVE-2026-8519 was first published on May 14, 2026, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8519 actively exploited?
CVE-2026-8519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8519?
CVE-2026-8519 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-8519?
A fix for CVE-2026-8519 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-8519 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8519

Explore →

Is Your Infrastructure Affected by CVE-2026-8519?

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

Book a Demo →Browse All CVEs