CVE-2025-13634: Google Chrome · Inappropriate Implementation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium : upgrade to 143.0.7499.41 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% 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:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 |
|---|---|---|
Googlegoogle/chromepkg:deb/google/chromeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should implement the following specific mitigation measures: 1) Immediately update Google Chrome on all Windows endpoints to version 143.0.7499.41 or later once available to ensure the vulnerability is patched. 2) Enforce strict endpoint security policies that limit local user privileges and restrict the ability to run or open untrusted HTML content or downloads. 3) Deploy application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious file executions that bypass MOTW protections. 4) Educate users about the risks of interacting with unknown or suspicious HTML pages, emphasizing caution with downloads and local content. 5) Utilize network-level protections such as web filtering to block access to potentially malicious sites hosting crafted HTML content. 6) Regularly audit and monitor local user activity and download behaviors to detect anomalies indicative of exploitation attempts. 7) Coordinate with IT teams to ensure timely deployment of Chrome updates and verify patch status across all endpoints. These measures go beyond generic advice by focusing on local user access controls, user awareness, and proactive monitoring tailored to the specific nature of this vulnerability.
Description
Inappropriate implementation in Downloads in Google Chrome on Windows prior to 143.0.7499.41 allowed a local attacker to bypass mark of the web via a crafted HTML page. (Chromium security severity: Medium)