CVE-2025-6554highunder attackCWE-843

CVE-2025-6554: high-severity vulnerability in Google Chrome

Published · Updated

78Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA and has a public proof of concept.

ssvc Actcvss 8.1epss 14%
from disclosure to weapon4 days
Published on NVDJun 30
1st PoC+4d
CISA KEV+2d
exploitation probability
14%top 3% of all CVEs
observed exploitation
yesCISA + VulnCheck
17 public exploit(s)
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Not affected
1 product — because the vulnerable code is not present in the product
red_hat_products
Action required by CISAfederal deadline: 2025-07-23

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

In short

A type confusion bug in Chrome's V8 JavaScript engine allows attackers to read and write arbitrary data on your computer through a malicious website. This happens because the browser incorrectly handles certain data types, giving attackers unauthorized access.

Technical detail

Type confusion vulnerability in V8 engine (CWE-843) enables arbitrary memory read/write operations when processing crafted HTML/JavaScript. Attack vector is remote via malicious webpage; requires user to visit attacker-controlled site. Impact includes potential code execution and sensitive data exfiltration.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

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)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Affected products
Google · Chrome
public PoCs found — 17
githubgithub.com/aklnjakln/CVE-2025-6554★ 31githubgithub.com/Muhammednihalmp/Google-chrome-zero-day★ 12githubgithub.com/gmh5225/CVE-2025-6554-2★ 2githubgithub.com/PwnToday/CVE-2025-6554★ 2githubgithub.com/ghostn4444/POC-CVE-2025-6554★ 1githubgithub.com/gmh5225/CVE-2025-6554★ 0githubgithub.com/LordBheem/CVE-2025-6554★ 0vulncheckvulncheck.com/xdb/df5a046851b7unverifiedvulncheckvulncheck.com/xdb/48e4631c2f7bunverifiedvulncheckvulncheck.com/xdb/249921793298unverifiedvulncheckvulncheck.com/xdb/a04d86222170unverifiedvulncheckvulncheck.com/xdb/6c862bba7ff9unverifiedvulncheckvulncheck.com/xdb/b770c56b6018unverifiedvulncheckvulncheck.com/xdb/ffb3aa35a137unverifiedvulncheckvulncheck.com/xdb/635a4a5ef944unverifiedvulncheckvulncheck.com/xdb/fb98908ab93bunverifiedvulncheckvulncheck.com/xdb/838924878d00unverified
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Google Chrome

In the same product, most dangerous first.

CVE-2023-4863HIGHCVE-2023-4863EPSS 100.0%KEVCVE-2018-17463HIGHCVE-2018-17463EPSS 84.6%KEVCVE-2021-21224HIGHCVE-2021-21224EPSS 84.2%KEVCVE-2020-6418HIGHCVE-2020-6418EPSS 78.8%KEVCVE-2022-2294HIGHCVE-2022-2294EPSS 70.8%KEVCVE-2021-21220HIGHCVE-2021-21220EPSS 70.4%KEV
References
https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_30.htmlhttps://issues.chromium.org/issues/427663123https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-6554