CVE-2025-6557: Google Chrome · Insufficient data validation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 138.0.7204.49 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 138.0.7204.49
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 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 2026-10-26.
What to do
Upgrade Google Chrome to 138.0.7204.49.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-6557, organizations should prioritize updating Google Chrome to version 138.0.7204.49 or later, where the vulnerability is addressed. Since the exploit requires user interaction with DevTools, educating users about the risks of interacting with suspicious web content and unsolicited prompts to open or use DevTools can reduce exposure. Implementing browser security policies that restrict or monitor DevTools usage in enterprise environments can further limit attack vectors. Network-level protections such as web filtering and intrusion detection systems can help block access to malicious crafted HTML pages. Additionally, employing endpoint detection and response (EDR) solutions to monitor for unusual process behaviors related to Chrome can aid in early detection of exploitation attempts. Regular vulnerability scanning and patch management processes should be enforced to ensure timely application of security updates. Finally, organizations should review and harden their security awareness training to include scenarios involving browser-based social engineering attacks.
Description
Insufficient data validation in DevTools in Google Chrome on Windows prior to 138.0.7204.49 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: Low)