CVE-2026-3537

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-04. 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%CVSS: 8.8Exploit: None knownExposed: 0

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

Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to potentially exploit heap corruption 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.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
31%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-3537(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 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 ... 145.0.7632.75-1~deb13u1 (318 versions)145.0.7632.159-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 145.0.7632.75-1~deb13u1 (84 versions)145.0.7632.159-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 145.0.7632.75-1~deb13u1 (85 versions)145.0.7632.159-1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 36× 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-09-10 09:34 UTCEPSS rescore
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-31 16:04 UTCOSV refresh
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 17:03 UTCEPSS rescore
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 20:56 UTCVendor advisory
Show 53 more
  1. 2026-08-14 20:56 UTCGHSA enrichment
  2. 2026-08-14 08:34 UTCEG score recompute
  3. 2026-08-14 08:34 UTCVendor advisory
  4. 2026-08-14 08:34 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 00:16 UTCEG score recompute
  7. 2026-08-13 00:16 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-11 23:14 UTCEG score recompute
  10. 2026-08-11 23:14 UTCVendor advisory
  11. 2026-08-11 23:14 UTCGHSA enrichment
  12. 2026-08-11 13:43 UTCEPSS rescore
  13. 2026-08-11 05:48 UTCEG score recompute
  14. 2026-08-11 05:48 UTCVendor advisory
  15. 2026-08-11 05:48 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 08:38 UTCVendor advisory
  18. 2026-08-10 08:38 UTCGHSA enrichment
  19. 2026-08-09 20:24 UTCEG score recompute
  20. 2026-08-09 20:24 UTCVendor advisory
  21. 2026-08-09 20:24 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 08:11 UTCEG score recompute
  24. 2026-08-09 08:11 UTCVendor advisory
  25. 2026-08-09 08:11 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 08:16 UTCVendor advisory
  28. 2026-08-08 08:16 UTCGHSA enrichment
  29. 2026-08-07 20:03 UTCEG score recompute
  30. 2026-08-07 20:03 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 02:40 UTCEG score recompute
  33. 2026-08-06 02:40 UTCVendor advisory
  34. 2026-08-06 02:40 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-04 02:34 UTCEG score recompute
  39. 2026-08-04 02:34 UTCVendor advisory
  40. 2026-08-04 02:34 UTCGHSA enrichment
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 18:57 UTCEG score recompute
  43. 2026-08-02 18:57 UTCVendor advisory
  44. 2026-08-02 18:57 UTCGHSA enrichment
  45. 2026-08-02 02:27 UTCEPSS rescore
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-27 14:13 UTCEPSS rescore
  50. 2026-07-27 12:54 UTCEG score recompute
  51. 2026-07-27 12:54 UTCVendor advisory
  52. 2026-07-27 12:54 UTCGHSA enrichment
  53. 2026-07-27 12:50 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-3537?
CVE-2026-3537 is a high vulnerability published on March 4, 2026. Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
When was CVE-2026-3537 disclosed?
CVE-2026-3537 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3537 actively exploited?
CVE-2026-3537 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 69.0% of all scored CVEs.
What is the CVSS score of CVE-2026-3537?
CVE-2026-3537 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-3537?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3537, 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-3537

Explore →

Is Your Infrastructure Affected by CVE-2026-3537?

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

Start Free Scan →Browse All CVEs