Skip to content
NewA calmer, faster ZeroHour
Exploit / PoCcriticalExploited in the wild

Google fixed the seventh Chrome zero

Security Affairsby @securityaffairs ()2 min read7 · 2 reads
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2025-10585
Actively Exploited V8 Type Confusion in Google Chrome (Heap Corruption)
9.89%KEV
KEV
CVE-2025-13223
Actively Exploited V8 Type Confusion in Google Chrome and Siemens Chromium Components
8.85%KEV
KEV
CVE-2025-13224
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
8.8<1%PoC
CVE-2025-2783
Sandbox Escape via Mojo Handle Flaw in Google Chrome on Windows (CVE-2025-2783)
8.39%KEV
KEV
CVE-2025-4664
Insufficient policy enforcement in Loader in Google Chrome prior to 136.0.7103.113 allowed a remote attacker to leak cross-origin data via a crafted HTML page
4.36%
CVE-2025-5419
Actively Exploited Out-of-Bounds Read/Write in Chromium V8 (Chrome, Edge)
8.87%KEV
KEV
CVE-2025-6554
Type Confusion in Google Chrome V8 Allows Arbitrary Read/Write (Actively Exploited)
8.114%KEV
KEV
CVE-2025-6558
Actively Exploited Input Validation Flaw in Chrome ANGLE/GPU Allows Sandbox Escape
8.811%KEV
KEV

From the original article

2 min read at securityaffairs.com

Google patched two Chrome flaws, including a V8 type-confusion bug, tracked as including CVE-2025-13223, which was exploited in the wild. Google released Chrome security updates to address two flaws, including a high-severity V8 type confusion bug tracked as CVE-2025-13223 that has been actively exploited in the wild.

Security Affairs

By @securityaffairs · securityaffairs.com

Read the full article at Security Affairs

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.