# CVE-2025-0611: Memory corruption in Chrome

> Remote attackers can exploit heap corruption in V8 via crafted HTML pages to potentially execute arbitrary code in Google Chrome.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2025
- **Updated:** 6 Feb 2025
- **Also known as:** AZL-56022, AZL-56041, DEBIAN-CVE-2025-0611, GHSA-83vc-v46q-mv3w, openSUSE-SU-2025:14848-1

## What is CVE-2025-0611?

CVE-2025-0611 is a high-severity memory corruption vulnerability in Google Chrome, published on 22 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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)

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-0611?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodejs-electron` | openSUSE:Tumbleweed | All versions | 33.4.2-1.1 |

Products: Google Chrome.

## How do I fix CVE-2025-0611?

Upgrade to a fixed version.

## Is CVE-2025-0611 being exploited?

There is no known exploitation of CVE-2025-0611 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0611 and fix it if it is affected.

What it is: CVE-2025-0611 is a high-severity memory corruption vulnerability in Google Chrome, published on 22 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0611 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0611/ (Markdown: https://insights.sbomify.com/CVE-2025-0611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0611
- OSV: https://osv.dev/vulnerability/CVE-2025-0611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0611/
Summaries are generated and may contain mistakes; the official description above is the record.