VulnerabilityPublished 17 Nov 2025Updated 26 Feb 2026

CVE-2025-13226: Google Chrome · Type Confusion

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.8High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% 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:H

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 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: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (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 or the CVSS exploit maturity 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

Affected software

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

AI-suggested

To mitigate CVE-2025-13226 effectively, organizations should: 1) Immediately update Google Chrome to version 142.0.7444.59 or later once patches are available, as this is the definitive fix for the vulnerability. 2) Employ enterprise browser management tools to enforce automatic updates and prevent use of outdated versions. 3) Implement network-level protections such as web filtering and intrusion prevention systems to block access to known malicious sites and suspicious HTML content. 4) Educate users about the risks of visiting untrusted websites and the importance of cautious browsing behavior to reduce the likelihood of triggering the exploit. 5) Utilize browser sandboxing and endpoint protection solutions that can detect and contain anomalous behavior resulting from exploitation attempts. 6) Monitor security advisories from Google and threat intelligence feeds for emerging exploit reports or indicators of compromise related to this vulnerability. 7) Consider deploying Content Security Policy (CSP) headers and disabling unnecessary browser extensions that could increase attack surface. These targeted actions go beyond generic advice by focusing on patch management, user awareness, and layered defenses specific to browser-based heap corruption attacks.

Description

Type Confusion in V8 in Google Chrome prior to 142.0.7444.59 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Impact

The exploitation of CVE-2025-13226 can have severe consequences for organizations worldwide. Successful attacks can lead to arbitrary code execution within the browser context, enabling attackers to bypass sandbox protections, execute malicious payloads, and potentially gain further access to internal networks or sensitive data. This can result in data breaches, loss of intellectual property, disruption of business operations, and compromise of user credentials. Because Chrome is a widely used browser across enterprises, government agencies, and individual users, the scope of impact is extensive. The vulnerability affects confidentiality by allowing unauthorized data access, integrity by enabling code manipulation, and availability by potentially causing crashes or denial of service. The requirement for user interaction (visiting a malicious page) means social engineering or drive-by download attacks are likely vectors. The absence of known exploits in the wild currently provides a window for mitigation, but the high severity score indicates that attackers may develop exploits rapidly once patches are available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 04:43 UTC

Technical details

References

Community reviews

Related threats