CVSS 3.1
9.6 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HCVE-2026-121189 google chrome: Use After Free
Critical (9.6) in google chrome. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
Use after free in Browser in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Severity
- 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-04. 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-416 Use After Free
- Published
- Modified
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-121189 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121189?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121189?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-121189 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
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:
[](https://cve.bz/cve/CVE-2026-121189)
HTML:
<a href="https://cve.bz/cve/CVE-2026-121189"><img src="https://cve.bz/cve/badge/CVE-2026-121189.svg" alt="CVE-2026-121189"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.38 before 157.0.8103.38 |
Fix and patched versions
- openSUSE: fixed package versions per release
- Vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | chromium | no fix listed | DEBIAN-CVE-2026-121189 |
| openSUSE | Tumbleweed | chromium | 157.0.8103.38-1.1 | openSUSE-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 Low.
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
--- 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 browser navigation to untrusted web content and enforce memory mitigations within the Chromium Browser component: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which resolves the use-after-free memory corruption flaw in the Browser component, closing crafted HTML page. Until patched, this is a concern on systems running Chromium rendering untrusted web content across any platform, so restrict user browsing to trusted sites and avoid opening untrusted HTML pages. As a compensating measure, Enforce Address Space Layout Randomization to randomize process memory and hinder address reuse, Enforce non-executable permissions on heap and data pages using the NX/XD bit to block injected shellcode execution, Enable Full RELRO and PIE to ensure position-independent layouts and make the Global Offset Table read-only, Enforce Control Flow Integrity and Shadow Call Stack to validate indirect call targets against vtable corruption, and Deploy Endpoint Detection and Response agents to detect anomalous code injection and unauthorized child process execution. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
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-121189.