CVE-2025-3619

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)

Published: 2025-04-16 Last update: 2025-07-15 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-3619 is rated Moderate Risk (46.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.13%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-3619

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-03 0.15% 0.13% -0.02%
2 2026-05-25 0.12% 0.15% +0.03%
3 2026-03-04 — 0.12% —

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-3619

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-3619

OS Trackers for CVE-2025-3619

vendor priority summary link
alpine — CVE-2025-3619: 2 source package rows (qt5-qtwebengine, qt6-qtwebengine); 5 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2025-3619
debian end-of-life CVE-2025-3619 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-3619
ubuntu medium CVE-2025-3619 medium priority: Ubuntu including 1 source packages (chromium-browser), 6 status rows across 6 suites (focal, jammy, noble, oracular, plucky, upstream): not-affected 4, DNE 1, released 1. https://ubuntu.com/security/CVE-2025-3619

Affected software / configurations for CVE-2025-3619

Vendor Product Version Raw CPE
google chrome < 135.0.7049.95 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2025-3619

cvelogic Threat Intelligence