CVE-2026-2650
Received
Received - Intake
Heap Buffer Overflow in Google Chrome Media Component
Publication date: 2026-02-18
Last updated on: 2026-02-19
Assigner: Chrome
Description
Description
Heap buffer overflow in Media in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chrome | to 145.0.7632.109 (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 the Media component of Google Chrome versions prior to 145.0.7632.109. It allows a remote attacker to potentially exploit heap corruption by using a specially crafted HTML page.
How can this vulnerability impact me? :
The vulnerability could allow a remote attacker to cause heap corruption, which might lead to unexpected behavior such as crashes or potentially allow execution of arbitrary code within the context of the browser.
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