CVE-2025-12430VulnerabilityPublished 10 Nov 2025Updated 12 Nov 2025

CVE-2025-12430: Google Chrome · Object lifecycle issue

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 142.0.7444.59 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% 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:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 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 2026-10-25.

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

European organizations should prioritize upgrading all Chrome installations to version 142.0.7444.59 or later as soon as the patch is available. Until then, consider implementing browser-level mitigations such as disabling or restricting media features if feasible, or using browser security extensions that can detect or block suspicious UI manipulations. Conduct targeted user awareness training focusing on recognizing UI spoofing and phishing attempts, emphasizing caution with unexpected or suspicious web content. Network-level defenses such as web filtering and intrusion detection systems should be tuned to identify and block malicious HTML pages exploiting this vulnerability. Organizations should also monitor threat intelligence feeds for any emerging exploit attempts related to CVE-2025-12430. Finally, enforce strict multi-factor authentication (MFA) policies to reduce the impact of credential theft resulting from UI spoofing attacks.

Description

Object lifecycle issue in Media in Google Chrome prior to 142.0.7444.59 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: High)

Impact

For European organizations, this vulnerability poses a significant risk to user trust and data confidentiality. Since Chrome is widely used across Europe in both enterprise and consumer environments, attackers could exploit this flaw to conduct phishing campaigns or social engineering attacks by spoofing legitimate UI elements. This could lead to credential theft, unauthorized access to sensitive systems, or the spread of malware. Sectors such as finance, healthcare, and government, which rely heavily on secure web communications, are particularly vulnerable. The lack of required user interaction lowers the barrier for exploitation, increasing the likelihood of successful attacks. Additionally, the widespread use of Chrome in remote work scenarios across Europe amplifies the potential impact. While availability and integrity are not directly compromised, the indirect consequences of successful UI spoofing could lead to broader security incidents and regulatory compliance issues under GDPR if personal data is compromised.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Nov 2025, 20:57 UTC

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats