CVE-2025-6554VulnerabilityPublished 30 Jun 2025Updated 21 Oct 2025

CVE-2025-6554: Google Chrome · Type Confusion

Affects Google ChromeSource CVE Database V5

Exploited in the wild · KEV due 23 Jul 2025 · 14% EPSS : apply the vendor's fix or mitigations to Google Chrome now.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 23 Jul 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 14.1% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 30 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 2 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Chrome
23 Jun 202522:30 UTC, 7 days before disclosure
CVE published
on cve.org
30 Jun 202521:14 UTC, t = 0
In Threat Radar
record ingested
30 Jun 202521:24 UTC, 10 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2 Jul 2025, 2 days after disclosure
KEV remediation due
US federal deadline
23 Jul 2025, 23 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Affected software

Product	Affected	Fixed in
Google Chrome	Affected =138.0.7204.96	Fixed in–

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)

Impact

The impact of CVE-2025-6554 is significant for organizations and users worldwide due to Google Chrome's extensive adoption as a primary web browser. Successful exploitation allows attackers to perform arbitrary read and write operations in the browser's memory space, potentially leading to data leakage, unauthorized data manipulation, or further exploitation such as privilege escalation or remote code execution. This can compromise user confidentiality and data integrity, especially in environments where sensitive information is accessed via the browser, including corporate networks, financial services, and government portals. The requirement for user interaction (visiting a malicious page) means phishing or drive-by download attacks could be vectors. The vulnerability does not impact availability directly but can be a stepping stone for more severe attacks. Organizations with large numbers of Chrome users, especially those with high-value targets or sensitive data, face increased risk. Additionally, the lack of known exploits in the wild currently provides a window for proactive patching before widespread attacks emerge.

Mitigation

To mitigate CVE-2025-6554, organizations and users should immediately update Google Chrome to version 138.0.7204.96 or later, where the vulnerability is patched. Beyond patching, organizations should implement strict browser security policies, including disabling or restricting JavaScript execution on untrusted or unknown websites using browser extensions or enterprise policies. Employing browser sandboxing and site isolation features can limit the impact of potential exploitation by isolating processes and reducing memory sharing. User education is critical to reduce the risk of social engineering attacks that lure users to malicious pages. Network-level protections such as web filtering and intrusion prevention systems can help block access to known malicious URLs. Monitoring browser behavior for anomalies and employing endpoint detection and response (EDR) solutions can aid in early detection of exploitation attempts. Regular vulnerability scanning and patch management processes should be enforced to ensure timely updates.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 15:40 UTC

WeaknessesCWE-843

Technical details

References

Community reviews

Related threats