CVE-2025-13223highunder attackCWE-843

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

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

51Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA.

ssvc Actcvss 8.8epss 4.9%
from disclosure to weapon
Published on NVDNov 17
CISA KEV+2d
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.

Not affected
1 product — because the vulnerable code is not present in the product
red_hat_products
Action required by CISAfederal deadline: 2025-12-10

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

V8 (Chrome's JavaScript engine) has a type confusion vulnerability that lets attackers trick it into mishandling memory through a malicious webpage, potentially corrupting the heap and crashing or controlling the browser.

Technical detail

Type confusion in V8's type system allows a remote attacker to trigger heap corruption via crafted HTML, leading to potential code execution or denial of service. The attack requires user interaction (visiting a malicious page) and affects Chrome versions prior to 142.0.7444.175.

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 142.0.7444.175 allowed a remote attacker to potentially exploit heap corruption 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:H
Affected products
Google · Chrome