CVE-2025-13639: Google Chrome · Inappropriate Implementation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 143.0.7499.41 soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% 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:NExploitation 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
- Immediately update all Google Chrome installations to version 143.0.7499.41 or later, as this version contains the fix for CVE-2025-13639.
- Implement strict Content Security Policies (CSP) on internal web applications to reduce the risk of malicious script execution.
- Educate users about the risks of clicking unknown or suspicious links, especially those received via email or messaging platforms.
- Employ browser security extensions or endpoint protection solutions that can detect and block malicious web content or scripts.
- Monitor network traffic for unusual outbound connections or data exfiltration attempts that could indicate exploitation.
- Conduct regular security audits and penetration testing focused on web browser security and WebRTC usage.
- For organizations with high security requirements, consider restricting WebRTC usage via browser policies or extensions until the patch is applied.
- Maintain an inventory of browser versions in use across the organization to ensure timely updates and compliance.
Description
Inappropriate implementation in WebRTC in Google Chrome prior to 143.0.7499.41 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: Low)