Skip to main content
Mallory
High

Heap Buffer Overflow in Google Chrome Codecs Sandbox Escape

IdentifiersCVE-2026-12019CWE-787· Out-of-bounds Write

CVE-2026-12019 is a high-severity heap buffer overflow / out-of-bounds write vulnerability in the Codecs component of Google Chrome and Chromium-based Chromium packages. It affects Google Chrome on Linux and ChromeOS prior to version 149.0.7827.115. The available vendor description states that a crafted HTML page can trigger the flaw, and that exploitation is relevant after the attacker has already compromised the renderer process. In that post-renderer-compromise context, the memory corruption bug in Codecs could be leveraged to cross Chrome's sandbox boundary and achieve a sandbox escape.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation could allow an attacker who already has code execution or equivalent control within the renderer process to escape the Chrome sandbox on affected Linux and ChromeOS systems. This would turn a renderer compromise into a broader browser security-boundary bypass and could enable follow-on arbitrary code execution in a more privileged context, as well as high-impact confidentiality, integrity, and availability consequences on the host.

Mitigation

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

No specific workaround or temporary mitigation was provided in the supplied content. Practical mitigation is to reduce exposure until patching by limiting use of affected Chrome/Chromium builds on Linux and ChromeOS, restricting access to untrusted web content where feasible, and using updated browser channels/packages as soon as available. Because exploitation requires prior renderer compromise, reducing exposure to renderer-compromise bugs may also lower risk, but patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Linux and ChromeOS to version 149.0.7827.115 or later. For Debian chromium, apply the vendor security updates referenced in DSA-6344-1, including 149.0.7827.114-1~deb12u1 for Debian oldstable (bookworm) or 149.0.7827.114-1~deb13u1 for Debian stable (trixie), or a newer patched package. Prioritize patching because this issue affects a sandbox boundary and is part of a broader Chrome security release.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
GoogleChromeosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.