CVE-2026-7912

MEDIUMNVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

Score 4.2 from GitHub Security Advisory published 2026-05-06. NVD baseline CVSS 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer overflow in GPU in Google Chrome on Android prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)

CVSS v3
4.2
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
4.2MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

Published

May 6, 2026

Last Modified

May 6, 2026

Advisory Details (2)

Auto-updated Aug 3, 2026
Patch available.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-7912(1)

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 ... 147.0.7727.55-1~deb13u1 (348 versions)
  • every version up to 148.0.7778.96-1~deb12u1: fixed in 148.0.7778.96-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb12u1 (114 versions)
  • every version up to 148.0.7778.96-1~deb13u1: fixed in 148.0.7778.96-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb13u1 (115 versions)
  • every version up to 148.0.7778.96-1: fixed in 148.0.7778.96-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 206 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:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:57 UTCEPSS rescore
  9. 2026-09-30 15:04 UTCEPSS rescore
  10. 2026-09-29 15:24 UTCEPSS rescore
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:28 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-22 16:01 UTCEPSS rescore
  18. 2026-09-21 21:09 UTCEPSS rescore
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-06 13:48 UTCEPSS rescore
  4. 2026-09-04 05:07 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-08-30 19:18 UTCEPSS rescore
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-26 14:47 UTCEPSS rescore
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 14:18 UTCEPSS rescore
  15. 2026-08-23 19:46 UTCEG score recompute
  16. 2026-08-23 19:46 UTCVendor advisory
  17. 2026-08-23 19:46 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:56 UTCEPSS rescore
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 12:52 UTCEG score recompute
  26. 2026-08-17 12:52 UTCVendor advisory
  27. 2026-08-17 12:52 UTCGHSA enrichment
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 04:50 UTCEG score recompute
  31. 2026-08-16 04:50 UTCVendor advisory
  32. 2026-08-16 04:50 UTCGHSA enrichment
  33. 2026-08-16 02:15 UTCEPSS rescore
  34. 2026-08-15 01:31 UTCEPSS rescore
  35. 2026-08-14 03:24 UTCEG score recompute
  36. 2026-08-14 03:24 UTCVendor advisory
  37. 2026-08-14 03:24 UTCGHSA enrichment
  38. 2026-08-13 22:00 UTCEPSS rescore
  39. 2026-08-12 16:58 UTCEG score recompute
  40. 2026-08-12 16:58 UTCVendor advisory
  41. 2026-08-12 16:58 UTCGHSA enrichment
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-11 13:43 UTCEPSS rescore
  44. 2026-08-11 09:19 UTCEG score recompute
  45. 2026-08-11 09:19 UTCVendor advisory
  46. 2026-08-11 09:19 UTCGHSA enrichment
  47. 2026-08-11 00:00 UTCEPSS rescore
  48. 2026-08-10 07:26 UTCEG score recompute
  49. 2026-08-10 07:26 UTCGHSA enrichment
  50. 2026-08-09 13:47 UTCEPSS rescore
  51. 2026-08-09 05:35 UTCEG score recompute
  52. 2026-08-09 05:35 UTCGHSA enrichment
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-08 03:43 UTCEG score recompute
  55. 2026-08-08 03:43 UTCGHSA enrichment
  56. 2026-08-07 01:52 UTCEG score recompute
  57. 2026-08-07 01:52 UTCVendor advisory
  58. 2026-08-07 01:52 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-05 22:19 UTCEG score recompute
  61. 2026-08-05 22:19 UTCVendor advisory
  62. 2026-08-05 22:19 UTCGHSA enrichment
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 19:17 UTCEPSS rescore
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-03 19:49 UTCEG score recompute
  68. 2026-08-03 19:49 UTCVendor advisory
  69. 2026-08-03 19:49 UTCGHSA enrichment
  70. 2026-08-03 10:36 UTCEPSS rescore
  71. 2026-08-02 05:01 UTCEG score recompute
  72. 2026-08-02 05:01 UTCVendor advisory
  73. 2026-08-02 05:01 UTCGHSA enrichment
  74. 2026-08-02 02:27 UTCEPSS rescore
  75. 2026-08-01 04:16 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7912?
CVE-2026-7912 is a medium vulnerability published on May 6, 2026. Integer overflow in GPU in Google Chrome on Android prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-7912 disclosed?
CVE-2026-7912 was first published on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7912 actively exploited?
CVE-2026-7912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7912?
CVE-2026-7912 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-7912?
A fix for CVE-2026-7912 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7912 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-7912

Explore →

Is Your Infrastructure Affected by CVE-2026-7912?

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

Book a Demo →Browse All CVEs