CVE-2026-3544
Received
Received - Intake
Heap Buffer Overflow in Chrome WebCodecs Enables Remote Exploit
Publication date: 2026-03-04
Last updated on: 2026-03-05
Assigner: Chrome
Description
Description
Heap buffer overflow in WebCodecs in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an out of bounds memory write 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 145.0.7632.159 (exc) | |
| chrome | to 145.0.7632.160 (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(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability impact me? :
The vulnerability can allow a remote attacker to write outside the bounds of allocated memory, which may lead to arbitrary code execution, crashes, or other unpredictable behavior in the affected browser.
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
Can you explain this vulnerability to me?
This vulnerability is a heap buffer overflow in the WebCodecs component of Google Chrome versions prior to 145.0.7632.159. It allows a remote attacker to perform an out of bounds memory write by using a specially crafted HTML page.
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70