CVE-2026-4448
Received
Received - Intake
Heap Buffer Overflow in Chrome ANGLE Enables Remote Exploit
Publication date: 2026-03-20
Last updated on: 2026-03-20
Assigner: Chrome
Description
Description
Heap buffer overflow in ANGLE in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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
KEV
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a heap buffer overflow in ANGLE, a component used in Google Chrome versions prior to 146.0.7680.153. It allows a remote attacker to potentially cause heap corruption by crafting a malicious HTML page.
How can this vulnerability impact me? :
Exploitation of this vulnerability could lead to heap corruption, which may allow an attacker to execute arbitrary code or cause a denial of service in the affected version of Google Chrome.
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
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70