cve.bz

CVE-2026-95284 google chrome: Heap-based Buffer Overflow

9.6 criticalEPSS 0.5%

Critical (9.6) in google chrome. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Buffer overflow in ANGLE in Google Chrome on on Android prior to 154.0.8037.57 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Severity

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-95284 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95284?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95284?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95284 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 154.0.8037.57 before 154.0.8037.57

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 14chromium154.0.8037.57-1DEBIAN-CVE-2026-95284
Debian13chromium154.0.8037.57-1~deb13u1DEBIAN-CVE-2026-95284
openSUSELeap 16.0chromium154.0.8037.97-bp160.1.1openSUSE-SU-2026:22023-1
openSUSETumbleweedchromium154.0.8037.57-1.1openSUSE-SU-2026:11888-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10firefoxNot affected
Red Hat Enterprise Linux 10thunderbirdNot affected
Red Hat Enterprise Linux 6webkitgtkOut of support scope
Red Hat Enterprise Linux 7firefoxNot affected
Red Hat Enterprise Linux 7webkitgtk3Out of support scope
Red Hat Enterprise Linux 7webkitgtk4Will not fix
Red Hat Enterprise Linux 8firefoxNot affected
Red Hat Enterprise Linux 8mozjs60Not affected
Red Hat Enterprise Linux 8thunderbirdNot affected
Red Hat Enterprise Linux 8webkit2gtk3Not affected
Red Hat Enterprise Linux 9firefoxNot affected
Red Hat Enterprise Linux 9thunderbirdNot affected
Red Hat Enterprise Linux 9webkit2gtk3Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-95284.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON