CVE-2025-3619
Google Chrome Heap Buffer Overflow Vulnerability
Description
Heap buffer overflow in Codecs in Google Chrome on Windows prior to 135.0.7049.95 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
INFO
Published Date :
April 16, 2025, 9:15 p.m.
Last Modified :
April 23, 2025, 6:12 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
2.8
Public PoC/Exploit Available at Github
CVE-2025-3619 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-3619.
| URL | Resource |
|---|---|
| https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_15.html | Vendor Advisory |
| https://issues.chromium.org/issues/409619251 | Issue Tracking Permissions Required |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
DSA and DLA for Debian last 14 days
Python
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-3619 vulnerability anywhere in the article.
-
Daily CyberSecurity
Perplexity Eyes Chrome as DOJ Pressures Google Over Antitrust
In addition to OpenAI expressing interest in acquiring Google’s Chrome browser business, Perplexity.ai has also signaled its intent to pursue such a deal. During testimony in the U.S. Department of Ju ... Read more
The following table lists the changes that have been made to the
CVE-2025-3619 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 23, 2025
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:google:chrome:*:*:*:*:*:windows:*:* versions up to (excluding) 135.0.7049.95 Added Reference Type Chrome: https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_15.html Types: Vendor Advisory Added Reference Type Chrome: https://issues.chromium.org/issues/409619251 Types: Issue Tracking, Permissions Required -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Apr. 17, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Added CWE CWE-122 -
New CVE Received by [email protected]
Apr. 16, 2025
Action Type Old Value New Value Added Description Heap buffer overflow in Codecs in Google Chrome on Windows prior to 135.0.7049.95 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical) Added CWE CWE-122 Added Reference https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_15.html Added Reference https://issues.chromium.org/issues/409619251
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-3619 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-3619
weaknesses.