Exploited vulnerabilities / CVE-2025-13223
Confirmed exploited · memory corruption · Google Chromium V8CVE-2025-13223
Google Chromium V8 memory corruption, confirmed exploited in the wild.
Google Chromium V8 contains a type confusion vulnerability that allows for heap corruption.
| CISA's name for it | Google Chromium V8 Type Confusion Vulnerability |
|---|---|
| Vendor and product | Google · Chromium V8 |
| Type | memory corruption · CWE-843 |
| Exploited | Confirmed by CISA listed 19 November 2025 |
| Likelihood | more likely to be exploited than most |
| Deadline | 10 December 2025 · already passed |
| Used in ransomware | Not reported |
| Advisories | chromereleases.googleblog.com ↗ · nvd.nist.gov ↗ |
Three steps, in this order
Update the product (and every browser or app that embeds it) to the fixed version.
Make sure automatic updates are on and actually applied; restart where the update needs it.
Watch endpoints for crashes and unusual child processes from the affected software.
| CISA's required action | Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. |
|---|
Know before someone else finds it
Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.
CVE-2025-13223 in short
Is CVE-2025-13223 being exploited?
Yes. CISA added CVE-2025-13223 to its Known Exploited Vulnerabilities catalogue on 19 November 2025, which it does only on evidence of exploitation in the wild.
What is the CISA deadline for CVE-2025-13223?
US federal agencies must remediate it by 10 December 2025. Everyone else should treat that date as the latest safe point to patch an internet-facing system.
How likely is CVE-2025-13223 to be exploited in the next 30 days?
FIRST's Exploit Prediction Scoring System gives it 4.9%, the 92nd percentile of every CVE it scores.
How do I fix CVE-2025-13223?
Update the product (and every browser or app that embeds it) to the fixed version. Make sure automatic updates are on and actually applied; restart where the update needs it. Watch endpoints for crashes and unusual child processes from the affected software.
Other Google vulnerabilities being exploited
| CVE | Product | Type | Listed |
|---|---|---|---|
| CVE-2026-125350 | Chromium | remote code execution | 10 November 2026 |
| CVE-2026-111497 | Brotli | remote code execution | 27 October 2026 |
| CVE-2026-58704 | Pixel | privilege escalation | 16 September 2026 |
| CVE-2026-87491 | Chromium V8 | remote code execution | 9 September 2026 |
| CVE-2026-85046 | Chromium V8 | remote code execution | 4 September 2026 |
| CVE-2026-11645 | Chromium V8 | remote code execution | 9 June 2026 |
Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.