CVE-2026-4464
Integer Overflow in Chrome ANGLE Causes Potential Heap Corruption
Publication date: 2026-03-20
Last updated on: 2026-03-20
Assigner: Chrome
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chrome | to 146.0.7680.153 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
| CWE-472 | The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an integer overflow in ANGLE, a component used in Google Chrome versions prior to 146.0.7680.153. An integer overflow occurs when a calculation exceeds the maximum size that can be stored in an integer variable, potentially leading to unexpected behavior.
In this case, the overflow could be exploited by a remote attacker through a specially crafted HTML page, which might cause heap corruption in the browser.
How can this vulnerability impact me? :
The vulnerability could allow a remote attacker to cause heap corruption in your browser by tricking you into visiting a maliciously crafted HTML page.
Heap corruption can lead to unpredictable behavior, including crashes or potentially arbitrary code execution, which might compromise the security of your system or data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know