# CVE-2025-6554: Google Chromium V8 Type Confusion

> A type confusion flaw in Chrome's V8 engine allows remote attackers to perform arbitrary read/write operations via a crafted HTML page.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 2 Jul 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jun 2025
- **Updated:** 21 Oct 2025
- **Also known as:** AZL-76320, DEBIAN-CVE-2025-6554, DSA-5955-1, GHSA-mj9c-f5v6-7665

## What is CVE-2025-6554?

CVE-2025-6554 is a high-severity memory corruption vulnerability in Google Chrome, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Type confusion in V8 in Google Chrome prior to 138.0.7204.96 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version. US federal agencies must fix it by 23 Jul 2025.

## Is CVE-2025-6554 being exploited?

Yes. Attackers have exploited CVE-2025-6554 in the wild since at least 2 Jul 2025.

Public exploit code:

- https://github.com/mistymntncop/CVE-2025-6554 (github_poc): https://github.com/mistymntncop/CVE-2025-6554
- https://github.com/aklnjakln/CVE-2025-6554 (github_poc): https://github.com/aklnjakln/CVE-2025-6554
- CVE-2025-6554 (github_poc): https://github.com/Muhammednihalmp/Google-chrome-zero-day
- poc for CVE-2025-6554 (github_poc): https://github.com/jopraveen/CVE-2025-6554
- https://github.com/gmh5225/CVE-2025-6554-2 (github_poc): https://github.com/gmh5225/CVE-2025-6554-2
- https://github.com/PwnToday/CVE-2025-6554 (github_poc): https://github.com/PwnToday/CVE-2025-6554

## 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-6554 and fix it if it is affected.

What it is: CVE-2025-6554 is a high-severity memory corruption vulnerability in Google Chrome, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-6554 in the wild since at least 2 Jul 2025.

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-6554/ (Markdown: https://insights.sbomify.com/CVE-2025-6554/index.md)
```

## Sources

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

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