CVE-2025-12434VulnerabilityPublished 10 Nov 2025

CVE-2025-12434: Google Chrome · Race

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.2 Medium : upgrade to 142.0.7444.59 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.2Medium

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 142.0.7444.59

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L

Attack Vector: Network
Attack Complexity: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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 10 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 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 142.0.7444.59.

Affected software

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

AI-suggested

1. Immediately update all Google Chrome installations on Windows to version 142.0.7444.59 or later to apply the fix addressing the race condition. 2. Implement enterprise-wide browser update policies to ensure timely patch deployment and prevent use of vulnerable versions. 3. Educate users about the risks of interacting with suspicious web pages and performing unusual UI gestures, emphasizing caution with unexpected prompts or UI changes. 4. Deploy browser security extensions or policies that restrict or monitor UI manipulations and scripting behaviors that could facilitate spoofing. 5. Use endpoint detection and response (EDR) tools to monitor for anomalous browser behaviors indicative of exploitation attempts. 6. Conduct phishing awareness campaigns tailored to highlight UI spoofing risks. 7. For high-risk environments, consider application whitelisting or sandboxing to limit the impact of potential browser-based attacks. 8. Monitor threat intelligence feeds for any emerging exploits targeting this vulnerability to adjust defenses accordingly.

Description

Race in Storage in Google Chrome on Windows prior to 142.0.7444.59 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 moderate risk primarily through UI spoofing attacks that can facilitate phishing and social engineering campaigns. While it does not directly compromise system confidentiality or integrity, successful exploitation can lead to credential theft, unauthorized transactions, or malware installation if users are deceived by the spoofed UI. Organizations with large numbers of Windows users running outdated Chrome versions are particularly vulnerable. Sectors such as finance, government, and critical infrastructure, where trust in browser UI is essential, may face increased risks. The need for user interaction limits automated exploitation but does not eliminate the threat, especially in environments with high user exposure to web content. The lack of known exploits in the wild reduces immediate risk but does not preclude future attacks. Failure to update Chrome promptly could result in targeted attacks leveraging this vulnerability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2025, 20:38 UTC

Technical details

References

Community reviews

Related threats