VulnerabilityPublished 10 Nov 2025

CVE-2025-12439: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: 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 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 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

The primary mitigation is to update Google Chrome on Windows systems to version 142.0.7444.59 or later, where the vulnerability has been fixed. Organizations should enforce automated patch management policies to ensure timely deployment of browser updates. Additionally, restricting local user permissions to prevent unauthorized file execution can reduce the risk of exploitation. Employing endpoint detection and response (EDR) solutions to monitor for suspicious file activities and memory access patterns can help detect potential exploitation attempts. Educating users about the risks of running untrusted files locally and implementing application whitelisting can further limit attack vectors. For high-security environments, consider isolating browser processes using sandboxing or virtualization technologies to contain potential memory exposure. Regular audits of local access controls and monitoring for insider threats will also help mitigate risk.

Description

Inappropriate implementation in App-Bound Encryption in Google Chrome on Windows prior to 142.0.7444.59 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: Medium)

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality, as sensitive information processed by Chrome could be exposed to local attackers. Organizations with shared or multi-user Windows environments, such as corporate offices, educational institutions, or public access terminals, are particularly vulnerable. The ability of an attacker to extract sensitive data from process memory could lead to credential theft, unauthorized access to internal systems, or leakage of proprietary information. Although remote exploitation is not possible, insider threats or malware that gains local foothold could leverage this vulnerability. This risk is heightened in sectors handling sensitive personal data under GDPR, such as finance, healthcare, and government agencies. The lack of known exploits reduces immediate risk, but the presence of a patchable flaw necessitates prompt remediation to prevent future exploitation. The impact on system integrity and availability is minimal, but the breach of confidentiality could have significant regulatory and reputational consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats