VulnerabilityPublished 6 Nov 2025

CVE-2025-11210: Google Chrome · Side-channel Information Leakage

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% 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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 141.0.7390.54.

Affected software

Product	Affected	Fixed in
Google Chrome	Affected =141.0.7390.54 <141.0.7390.54	Fixed in 141.0.7390.54

AI-suggested

Immediately update all Google Chrome installations to version 141.0.7390.54 or later, where the vulnerability is addressed.
Implement enterprise-wide browser update policies to ensure timely patch deployment.
Educate users about the risks of interacting with suspicious web content and performing unexpected UI gestures prompted by websites.
Employ browser security extensions or enterprise security solutions that can detect and block UI spoofing attempts.
Monitor network traffic and user behavior for signs of phishing or social engineering campaigns exploiting this vulnerability.
Use multi-factor authentication (MFA) to reduce the impact of credential theft resulting from UI spoofing.
Conduct regular security awareness training focusing on recognizing deceptive UI elements and phishing tactics.
For high-risk environments, consider restricting browser usage to managed and monitored devices only.

Description

Side-channel information leakage in Tab in Google Chrome prior to 141.0.7390.54 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality and integrity of information accessed via Google Chrome. Attackers could leverage UI spoofing to trick users into revealing credentials, sensitive corporate data, or performing unauthorized transactions. Sectors such as finance, government, healthcare, and critical infrastructure that rely heavily on Chrome for web access are particularly vulnerable. The requirement for user interaction reduces the likelihood of automated mass exploitation but does not eliminate targeted phishing or social engineering attacks. The absence of availability impact means systems remain operational, but the trustworthiness of user interactions is compromised. Given the widespread use of Chrome across Europe, a successful attack could lead to data breaches, fraud, and reputational damage. Organizations with stringent compliance requirements (e.g., GDPR) may face regulatory consequences if user data confidentiality is compromised.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Nov 2025, 02:29 UTC

Technical details

References

Community reviews

Related threats