VulnerabilityPublished 7 Nov 2025Updated 10 Nov 2025

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

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 15:59 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 8% 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

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

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: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 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 140.0.7339.80.

Affected software

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

AI-suggested

Immediate update of all Google Chrome installations on Android devices to version 140.0.7339.80 or later to ensure the vulnerability is patched.
Implement mobile device management (MDM) solutions to enforce browser updates and monitor device compliance within the organization.
Conduct targeted user awareness training focusing on recognizing phishing attempts and suspicious download prompts, emphasizing caution when interacting with unknown or unsolicited HTML content.
Deploy advanced email and web filtering solutions to detect and block malicious URLs or attachments that could host crafted HTML pages exploiting this vulnerability.
Encourage the use of multi-factor authentication (MFA) to reduce the impact of credential compromise resulting from phishing attacks facilitated by domain spoofing.
Monitor network traffic and endpoint logs for unusual download activities or access to suspicious domains that may indicate exploitation attempts.
Coordinate with security teams to include this vulnerability in threat hunting and incident response playbooks, ensuring rapid detection and containment if exploitation occurs.

Description

Insufficient validation of untrusted input in Downloads in Google Chrome on Android prior to 140.0.7339.80 allowed a remote attacker to perform domain spoofing via a crafted HTML page. (Chromium security severity: Low)

Impact

For European organizations, this vulnerability primarily threatens user confidentiality by enabling attackers to conduct domain spoofing attacks that can deceive employees into divulging sensitive information or downloading malicious payloads. Given the widespread use of Google Chrome on Android devices across Europe, especially in corporate environments where mobile device usage is prevalent, the risk of successful phishing campaigns increases. This can lead to credential compromise, unauthorized access to corporate resources, and potential lateral movement within networks. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of successful social engineering attacks can be severe, including data breaches and financial losses. Organizations with remote or mobile workforces are particularly vulnerable, as attackers can exploit this flaw to target users outside traditional network perimeters. The absence of known active exploits provides a window for mitigation, but the medium severity rating underscores the need for timely patching and user awareness to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Nov 2025, 00:23 UTC

Technical details

References

Community reviews

Related threats