CVE-2026-19167

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.1Exploit: None knownExposed services: Not assessed

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

Integer overflow in GPU in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

CVSS v3
3.1
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/100CISA SSVC

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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

August 7, 2026

References (2)

Vendor Advisories for CVE-2026-19167(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 rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (503 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 151.0.7922.71-1~deb13u1 (397 versions)
  • every version up to 151.0.7922.108-1~deb12u1: fixed in 151.0.7922.108-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (163 versions)
  • every version up to 151.0.7922.108-1~deb13u1: fixed in 151.0.7922.108-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (164 versions)
  • every version up to 151.0.7922.108-1: fixed in 151.0.7922.108-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19167?
CVE-2026-19167 is a low vulnerability published on August 6, 2026. Integer overflow in GPU in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-19167 disclosed?
CVE-2026-19167 was first published 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-19167 actively exploited?
CVE-2026-19167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19167?
CVE-2026-19167 has a CVSS v3.1 base score of 3.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19167?
No fix for CVE-2026-19167 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-19167 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-19167

Explore →

Is Your Infrastructure Affected by CVE-2026-19167?

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

Book a Demo →Browse All CVEs