Skip to content
Fencer Intel
high 8.8

CVE-2026-3537 json

Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to potentially exploit heap…

published 8mo ago modified 4mo ago also EUVD-2026-9485

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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)

Patch / fix

  • google chrome 145.0.7632.159
  • chromium Debian 12 145.0.7632.159-1~deb12u1
  • chromium Debian 13 145.0.7632.159-1~deb13u1
  • chromium Debian 14 145.0.7632.159-1

debian advisories DEBIAN-CVE-2026-3537

  • chromium openSUSE Leap 16.0 145.0.7632.159-bp160.1.1
  • chromium openSUSE Tumbleweed 145.0.7632.159-1.1

opensuse advisories openSUSE-SU-2026:20332-1openSUSE-SU-2026:10296-1

  • chromium Alpine 3.24, Alpine 3.23 144.0.7559.132-r4

alpine advisories ALPINE-CVE-2026-3537

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-3537 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
8mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-1091 Use of Object without Invoking Destructor Method
  • CWE-787 Out-of-bounds Write
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.