Skip to main content
Mallory
CriticalVulnerability

CVE-2026-131031: Out-of-bounds write in Google Chrome GPU enabling sandbox escape

Published Nov 17, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 5 in a dayToday
CVSS9.6Critical · v3.1
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-131031CWE-787 · Out-of-bounds Write

CVE-2026-131031 is a critical out-of-bounds write vulnerability in the GPU component of Google Chrome before version 158.0.8127.36. Processing a crafted HTML page can corrupt memory and allow a remote attacker to execute arbitrary code outside the browser sandbox. The specific vulnerable function and triggering graphics operations have not been disclosed.

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 outside Chrome's sandbox, potentially compromising data confidentiality and integrity and disrupting system availability within the privileges of the compromised process. The vulnerability does not establish elevated operating-system privileges or full device control.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 158.0.8127.36 or later. Fixed release builds include 158.0.8127.36 for Linux and 158.0.8127.36 or 158.0.8127.37 for Windows and macOS. Restart Chrome after installation and verify the running version across managed devices. For distribution-packaged Chromium, check the distribution's security updates for a fixed package; the identified Debian package record lists the vulnerability as unpatched.

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.
FAQ

Frequently asked questions

Is CVE-2026-131031 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-131031 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-131031?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-131031.
Is there a patch for CVE-2026-131031?
Upgrade Google Chrome to version 158.0.8127.36 or later. Fixed release builds include 158.0.8127.36 for Linux and 158.0.8127.36 or 158.0.8127.37 for Windows and macOS.
How severe is CVE-2026-131031?
CVE-2026-131031 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 0.41% (36th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity5Community discussion across Reddit, Mastodon, and other social sources.