Skip to main content
Mallory
HighVulnerability

CVE-2026-118351: Skia Memory Corruption in Google Chrome

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

CVE-2026-118351 is a memory-corruption vulnerability, identified as a use-after-free, in the Skia graphics component of Google Chrome before version 156.0.8078.73. A remote attacker can trigger the flaw through a crafted HTML page and execute arbitrary code. Chromium rates the vulnerability High. The affected function and detailed memory-lifetime failure are not specified. Descriptions disagree on whether execution occurs inside or outside the browser sandbox, so sandbox escape is not conclusively 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.

Successful exploitation permits arbitrary code execution and can compromise confidentiality, integrity, and availability within the affected execution context. Execution inside the browser sandbox is explicitly documented; execution outside the sandbox is also claimed but conflicts with other vulnerability-specific descriptions. Unrestricted host compromise should therefore not be assumed.

Mitigation

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

No vulnerability-specific workaround is established. Until updates are deployed, reduce exposure to untrusted web content through web filtering and browsing restrictions. Run browsers without administrative privileges and retain sandboxing and available anti-exploitation protections. These defense-in-depth measures do not correct the vulnerability or establish protection against exploitation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome and affected Chromium packages to version 156.0.8078.73 or later, then relaunch the browser. Upgrade Microsoft Edge to version 156.0.4314.58 or later, preferably the latest supported release. For affected WebKitGTK installations, apply the platform vendor's security updates; identified fixed Red Hat packages are webkit2gtk3 2.54.2-2.el8_10 for RHEL 8 and 2.54.2-0.el9_8.2 for RHEL 9. Debian stable (trixie) provides fixed Chromium packages in version 156.0.8078.73-1~deb13u1. Use distribution-specific updates rather than applying Chrome version thresholds to WebKitGTK.

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-118351 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-118351 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-118351?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-118351.
Is there a patch for CVE-2026-118351?
Upgrade Google Chrome and affected Chromium packages to version 156.0.8078.73 or later, then relaunch the browser. Upgrade Microsoft Edge to version 156.0.4314.58 or later, preferably the latest supported release.
What products are affected by CVE-2026-118351?
Google Chrome.
How severe is CVE-2026-118351?
CVE-2026-118351 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.26% (19th 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.