CVE-2025-0611

CVE-2025-0611 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-122.

Key facts

Description

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)

Frequently asked questions

What is 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)
How severe is CVE-2025-0611?
CVE-2025-0611 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
Is CVE-2025-0611 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-0611?
CVE-2025-0611 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-0611?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-0611 have an EU (EUVD) identifier?
Yes. CVE-2025-0611 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-1789.
When was CVE-2025-0611 published?
CVE-2025-0611 was published on 2025-01-22 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Chrome

All CVEs affecting Google Chrome →

Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities

Browse all CWE-122 (Heap-based Buffer Overflow) vulnerabilities →