Skip to main content
VulnerabilityPublished Updated

CVE-2025-12905: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium : upgrade to 140.0.7339.80 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
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 140.0.7339.80
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 140.0.7339.80.

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =140.0.7339.80
  • <140.0.7339.80
Fixed in
  • 140.0.7339.80

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately update all Google Chrome installations on Windows to version 140.0.7339.80 or later to ensure the vulnerability is patched. 2) Enforce strict endpoint security policies that include application whitelisting and behavior-based detection to identify and block suspicious file executions that bypass MotW. 3) Enhance user awareness training focusing on the risks of interacting with untrusted downloads and phishing attempts, emphasizing caution with unexpected HTML content or downloads. 4) Utilize network security controls such as web filtering and sandboxing to detect and block access to malicious websites hosting crafted HTML pages. 5) Monitor logs and alerts for unusual download or execution patterns that may indicate exploitation attempts. 6) Consider deploying browser security extensions or enterprise policies that reinforce MotW or equivalent download protections. 7) Regularly review and update incident response plans to include scenarios involving MotW bypass and related download-based attacks. These targeted actions go beyond generic advice by focusing on the specific nature of the vulnerability and its exploitation vector.

Description

Inappropriate implementation in Downloads in Google Chrome on Windows prior to 140.0.7339.80 allowed a remote attacker to bypass Mark of the Web via a crafted HTML page. (Chromium security severity: Low)

References

Community reviews

Loading reviews…