Skip to main content
VulnerabilityPublished Updated

CVE-2025-12907: Google Chrome · Insufficient Validation of Untrusted Input

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =140.0.7339.80
Fixed in–

AI-suggested

To mitigate CVE-2025-12907, organizations and users should immediately update Google Chrome to version 140.0.7339.80 or later, where the vulnerability has been patched. Beyond patching, organizations should implement strict policies restricting access to DevTools, especially on managed devices, to reduce the risk of exploitation via user interaction. User education is critical; training should emphasize the dangers of interacting with untrusted web content or scripts within DevTools. Employ endpoint protection solutions capable of detecting anomalous behavior indicative of exploitation attempts. Network-level controls such as web filtering and intrusion prevention systems can help block access to known malicious sites that might attempt to exploit this vulnerability. For high-security environments, consider disabling or limiting DevTools usage to trusted personnel only. Regularly audit browser extensions and configurations to ensure they do not introduce additional risks. Finally, maintain robust incident response plans to quickly address any suspected exploitation.

Description

Insufficient validation of untrusted input in Devtools in Google Chrome prior to 140.0.7339.80 allowed a remote attacker to execute arbitrary code via user action in Devtools. (Chromium security severity: Low)

References

Community reviews

Loading reviews…