cve.bz

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

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
Buffer overflow in Skia 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: High)

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; 40th 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-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

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

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-121086](https://cve.bz/cve/badge/CVE-2026-121086.svg)](https://cve.bz/cve/CVE-2026-121086)

HTML:

<a href="https://cve.bz/cve/CVE-2026-121086"><img src="https://cve.bz/cve/badge/CVE-2026-121086.svg" alt="CVE-2026-121086"></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, 13chromiumno fix listedDEBIAN-CVE-2026-121086
Debian14libskia, chromiumno fix listedDEBIAN-CVE-2026-121086
Red Hatenterprise_linux:8::appstreamwebkit2gtk3, webkit2gtk3-jsc, webkit2gtk3-devel and 6 more0:2.54.2-3.el8_10RHSA-2026:99702
Red Hatenterprise_linux:9::appstreamwebkit2gtk3, webkit2gtk3-jsc, webkit2gtk3-devel and 6 more0:2.54.2-3.el9_9RHSA-2026:99132
Red Hatrhel_eus:9.8::appstreamwebkit2gtk3, webkit2gtk3-jsc, webkit2gtk3-devel and 6 more0:2.54.2-0.el9_8.3RHSA-2026:99131
openSUSETumbleweedchromium157.0.8103.38-1.1openSUSE-SU-2026:12426-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat · 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 isolate and restrict untrusted web content rendering within the Skia graphics component: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which fixes a heap-based buffer overflow in the Skia graphics rendering library, closing crafted HTML page. Until patched, this is a concern on Chromium and Google Chrome desktop deployments across all platforms, so restrict user browsing to trusted sites and avoid opening untrusted or unverified links. As a compensating measure, Enable Address Space Layout Randomization to randomize userspace memory addresses and hinder locating shellcode or ROP gadgets, Deploy EDR agents to detect anomalous process execution, memory injection, or lateral movement patterns escaping browser processes, and Enforce NX/XD bit non-executable memory permissions on the heap to block direct shellcode execution in corrupted buffers. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap-based buffer overflow — apply the upstream patch to fully remediate.

Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 9webkit2gtk3-0:2.54.2-3.el9_9Fixed 2026-11-11RHSA-2026:99132
Red Hat Enterprise Linux 9.8 Extended Update Supportwebkit2gtk3-0:2.54.2-0.el9_8.3Fixed 2026-11-12RHSA-2026:99131
Red Hat Enterprise Linux 10firefoxNot 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 8webkit2gtk3Affected
Red Hat Enterprise Linux 9firefoxNot 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-121086.

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