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

Integer Overflow in ANGLE in Google Chrome

IdentifiersCVE-2026-4452CWE-190· Integer Overflow or Wraparound

CVE-2026-4452 is a high-severity integer overflow vulnerability in ANGLE in Google Chrome on Windows prior to 146.0.7680.153. According to the provided content, a remote attacker could trigger the flaw via a crafted HTML page, leading to heap corruption. ANGLE is part of Chrome’s graphics stack, and the issue is described as an integer overflow that can corrupt heap memory during processing of attacker-controlled web content. No vulnerable function or code path is identified in the provided material.

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 may allow a remote, unauthenticated attacker to corrupt heap memory in the browser process by convincing a victim to visit a maliciously crafted webpage. Based on the supplied context for this Chrome release, memory corruption vulnerabilities of this class may result in arbitrary code execution, denial of service through browser crash, or potentially other security impacts depending on exploitability and runtime conditions.

Mitigation

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

Until patching is completed, reduce exposure by limiting access to untrusted websites and web content, especially attacker-controlled HTML pages. Standard browser hardening measures such as restricting unnecessary browsing from sensitive systems and using Chrome’s latest stable channel can reduce risk, but no specific vendor mitigation beyond updating is provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later on Windows. The broader Chrome stable update referenced in the provided content includes 146.0.7680.153 and 146.0.7680.154 for Windows and macOS, and 146.0.7680.153 for Linux. Applying the vendor-provided update is the primary remediation.
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 activity3

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