CVE-2025-13720: Google Chrome · Bad Cast
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 143.0.7499.41 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 143.0.7499.41
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 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.
What to do
Upgrade Google Chrome to 143.0.7499.41.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-13720, organizations should immediately update all Google Chrome installations to version 143.0.7499.41 or later, where the vulnerability is patched. Beyond patching, implement strict browser security policies such as disabling or restricting JavaScript execution from untrusted sources, employing Content Security Policy (CSP) headers to limit the impact of malicious HTML content, and using browser isolation technologies to contain potential compromises. Monitoring and logging renderer process behavior can help detect anomalous activity indicative of exploitation attempts. Employ endpoint detection and response (EDR) solutions capable of identifying heap corruption or unusual memory operations. User education to recognize phishing and suspicious links is critical to reduce the likelihood of user interaction with malicious content. Additionally, consider deploying network-level protections such as web filtering and sandboxing to intercept malicious web content before it reaches end users. Regularly review and update incident response plans to include browser-based exploit scenarios.
Description
Bad cast in Loader in Google Chrome prior to 143.0.7499.41 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)