CVE-2025-11213: Google Chrome · Inappropriate implementation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 141.0.7390.54 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 141.0.7390.54
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 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-25.
What to do
Upgrade Google Chrome to 141.0.7390.54.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
The primary mitigation is to update Google Chrome on all Android devices to version 141.0.7390.54 or later, where the vulnerability is fixed. Organizations should enforce mobile device management (MDM) policies to ensure timely updates and prevent the use of outdated browser versions. User education is critical: train users to recognize suspicious UI behaviors and avoid performing unusual gestures or interactions on untrusted websites. Implement multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing. Employ endpoint protection solutions that can detect and block access to known malicious URLs or phishing sites. Additionally, organizations should monitor network traffic for signs of phishing campaigns exploiting this vulnerability and conduct regular security awareness campaigns emphasizing safe browsing practices on mobile devices.
Description
Inappropriate implementation in Omnibox in Google Chrome on Android prior to 141.0.7390.54 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform domain spoofing via a crafted HTML page. (Chromium security severity: Medium)