CVE-2025-0611

Object corruption in V8 in Google Chrome prior to 132.0.6834.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

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

CVE-2025-0611 is rated Moderate Risk (57/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.64%). 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-0611

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-04-13 1.09% 0.64% -0.45%
2 2026-04-11 0.62% 1.09% +0.47%
3 2026-03-02 — 0.62% —

Full EPSS history (15 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-0611

OS Trackers for CVE-2025-0611

vendor priority summary link
alpine — CVE-2025-0611: 1 source package rows (qt6-qtwebengine); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-0611
debian end-of-life CVE-2025-0611 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-0611
ubuntu medium CVE-2025-0611 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (focal, jammy, noble, oracular, upstream): not-affected 3, DNE 1, released 1. https://ubuntu.com/security/CVE-2025-0611

Affected software / configurations for CVE-2025-0611

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

References for CVE-2025-0611

cvelogic Threat Intelligence