Skip to main content
Mallory
MediumVulnerability

CVE-2026-118319: 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
CVSS4.3Medium · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Google
IdentifiersCVE-2026-118319CWE-190 · Integer Overflow or Wraparound

CVE-2026-118319 is a vulnerability in the Skia graphics component affecting Google Chrome before version 156.0.8078.73. It is characterized as an integer overflow in one description and more generally as memory corruption in other advisories. A remote attacker can trigger the flaw through a crafted HTML page. Reported potential consequences differ: arbitrary code execution inside the browser sandbox or disclosure of memory within the sandbox. Chromium rates the vulnerability High. The affected function and precise corruption mechanism are not available.

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.

Exploitation may disclose memory within the browser sandbox. An alternative vulnerability description identifies potential arbitrary code execution within the sandbox, but this consequence is not consistently corroborated across the vulnerability-specific advisories. Sandbox escape, host-level code execution, and privilege escalation are not established.

Mitigation

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

No vulnerability-specific workaround is documented. Pending patching, reduce exposure to untrusted web content using website filtering and browsing restrictions. Retain browser sandboxing and available anti-exploitation protections, and run the browser without administrative privileges. These measures reduce exposure or potential downstream impact but do not correct the flaw.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 156.0.8078.73 or later and relaunch the browser. Upgrade Microsoft Edge to version 156.0.4314.58 or later. For Debian 13, update Chromium and related packages to 156.0.8078.73-1~deb13u1 or later. Apply the applicable vendor security updates for other Chromium distributions and affected WebKitGTK packages; Red Hat fixes include webkit2gtk3 2.54.2-2.el8_10 for RHEL 8 and 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-118319 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-118319 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-118319?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-118319.
Is there a patch for CVE-2026-118319?
Upgrade Google Chrome to version 156.0.8078.73 or later and relaunch the browser. Upgrade Microsoft Edge to version 156.0.4314.58 or later.
What products are affected by CVE-2026-118319?
Google Chrome.
How severe is CVE-2026-118319?
CVE-2026-118319 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.21% (11th 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.