VDB

CVE-2025-0611

CVE-2025-0611 PUBLISHED CVSS 8.2 HIGH

Reported by chrome · Published January 22, 2025

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)

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromiumChainguard132.0.6834.153-r0
qt6-qtwebengineAlpine6.8.2-r3
chromiumWolfi132.0.6834.153-r0
chromegoogle132.0.6834.110

Risk scores

CVSS 3.1
8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Affected products

VendorProductVersions
GoogleChrome132.0.6834.110
GoogleChrome132.0.6834.110

Timeline

  • Jan 22, 2025 PoC Published (8 in total, the first dated here)
  • Jan 22, 2025 CVE Published
  • Jan 23, 2025 EPSS Score (30 in total, the first dated here)
  • Feb 23, 2025 Coalition ESS Score (9 in total, the first dated here)
  • Jun 2, 2026 Security Advisory (6 in total, the first dated here)
  • Jun 17, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-0611
vulnetix vdb fixes CVE-2025-0611

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-0611/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›