Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Heap Buffer Overflow in Google Chrome Codecs

IdentifiersCVE-2026-2314CWE-122· Heap-based Buffer Overflow

CVE-2026-2314 is a high-severity heap-based buffer overflow in the Codecs component of Google Chrome affecting versions prior to 145.0.7632.45. The vulnerability can be triggered when a user visits a crafted HTML page, leading to heap corruption in the browser process. Chromium describes the issue as a heap buffer overflow in Codecs and rates it High severity. The available reporting indicates the flaw is remotely reachable via web content and may be exploitable for code execution.

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 can cause heap corruption in Chrome and may result in browser process compromise. Based on the provided sources, impact includes denial of service through browser crashes and the potential for arbitrary code execution in the browser context, with high impact to confidentiality, integrity, and availability reflected in the cited CVSS v3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Mitigation

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

If immediate patching is not possible, reduce exposure to untrusted web content by restricting browsing to trusted sites, applying URL filtering or web isolation controls, and using additional containment such as application sandboxing, VDI, or browser isolation. These measures may reduce exploitability or limit post-exploitation impact, but they are not substitutes for installing the fixed version.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 145.0.7632.45 or later. For Windows and macOS, update to 145.0.7632.45/46 as provided by Google’s stable channel release. If using downstream Chromium packages, apply the vendor-supplied fixed builds for the relevant platform or distribution.
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

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 activity9

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