Skip to main content
Mallory
HighVulnerability

CVE-2026-119271: Memory-safety vulnerability in Chromium Skia

Published Oct 30, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days39 mentions · peak 9 in a dayToday
CVSS8.8High · v3.1
EPSS0.22%13th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Google
IdentifiersCVE-2026-119271CWE-416 · Use After Free

CVE-2026-119271 is a high-severity memory-safety vulnerability in the Skia graphics component affecting Google Chrome before version 156.0.8078.79 and Chromium-based browsers. Its classification and exploitation conditions are inconsistent: it is characterized both as a use-after-free permitting arbitrary code execution inside the browser sandbox through a crafted HTML page, and as an uninitialized-resource flaw permitting an attacker who has already compromised the renderer process to read memory outside the sandbox. The precise vulnerable function and the relationship between these two characterizations are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Potential impacts include arbitrary code execution within the browser sandbox or disclosure of memory outside the sandbox. The outside-sandbox memory-read scenario requires prior renderer compromise. These outcomes have conflicting technical characterizations and should not be treated as a confirmed combined exploit chain. Code execution outside the sandbox is not established.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary mitigation or workaround is documented.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 156.0.8078.79 or later, using the applicable platform security release. Update Microsoft Edge to the latest available release incorporating the Chromium fix; conflicting version references prevent identifying a single reliable minimum fixed Edge version. For Debian stable (trixie), install Chromium 156.0.8078.79-1~deb13u1 or later. Apply the corresponding vendor security updates to other affected Chromium-based browsers and distribution packages. For affected RHEL WebKitGTK installations, RHSA-2026:96080 provides version 2.54.2-2.el8_10 for RHEL 8, and RHSA-2026:95194 provides version 2.54.2-0.el9_8.2 for RHEL 9.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2026-119271 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-119271 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-119271?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-119271.
Is there a patch for CVE-2026-119271?
Upgrade Google Chrome to version 156.0.8078.79 or later, using the applicable platform security release. Update Microsoft Edge to the latest available release incorporating the Chromium fix; conflicting version references prevent identifying a single reliable minimum fixed Edge version.
What products are affected by CVE-2026-119271?
Google Chrome.
How severe is CVE-2026-119271?
CVE-2026-119271 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.22% (13th percentile) as of Nov 12, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.