cve.bz

CVE-2026-121229 google chrome

9.6 criticalEPSS 0.4%

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

On this page
Memory corruption in ANGLE in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially 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.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-13. 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-11-03. 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-121229 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121229?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121229?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-121229 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.

Badge for a README or a site

CVE-2026-121229

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-121229](https://cve.bz/cve/badge/CVE-2026-121229.svg)](https://cve.bz/cve/CVE-2026-121229)

HTML:

<a href="https://cve.bz/cve/CVE-2026-121229"><img src="https://cve.bz/cve/badge/CVE-2026-121229.svg" alt="CVE-2026-121229"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 157.0.8103.38 before 157.0.8103.38

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14chromiumno fix listedDEBIAN-CVE-2026-121229
openSUSETumbleweedchromium157.0.8103.38-1.1openSUSE-SU-2026:12426-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.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-04) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to prevent rendering of untrusted web content or isolate the Chromium GPU process to limit memory corruption within the ANGLE graphics abstraction layer: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which vendor restricted specific bug details; resolves memory corruption within the ANGLE component, closing crafted HTML page. Until patched, this is a concern on Chromium deployments across all supported operating systems, so Restrict users from browsing untrusted sites or opening untrusted HTML pages that trigger ANGLE graphics processing. As a compensating measure, Enforce Address Space Layout Randomization to hinder reliable code-reuse attacks against the ANGLE userspace process, Enable the NX/XD bit to prevent execution of injected shellcode in corrupted data memory regions, Enforce full RELRO and PIE to ensure a read-only Global Offset Table and randomized binary code addresses, Enable Control Flow Integrity and Shadow Call Stack to validate indirect calls and return addresses in ANGLE, Apply kernel-level seccomp syscall filtering to constrain system calls accessible to compromised browser or GPU processes, and Deploy EDR agents to monitor for anomalous process activity and post-exploitation behavior escaping the sandbox. These controls limit blast radius and contain exploitation, but they do not fix the underlying memory corruption defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-601 Kernel-Level Syscall Filtering (seccomp) (medium)

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 7webkitgtk4Affected
Red Hat Enterprise Linux 8firefoxNot affected
Red Hat Enterprise Linux 8mozjs60Not affected
Red Hat Enterprise Linux 8thunderbirdNot affected
Red Hat Enterprise Linux 8webkit2gtk3Affected
Red Hat Enterprise Linux 9firefoxNot affected
Red Hat Enterprise Linux 9thunderbirdNot affected
Red Hat Enterprise Linux 9webkit2gtk3Affected

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-121229.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON