CVE-2025-12910VulnerabilityPublished 7 Nov 2025Updated 10 Nov 2025

CVE-2025-12910: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.2Medium

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

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

Attack Vector: Local
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: 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: 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 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 2026-10-26.

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 140.0.7339.80.

Affected software

Product	Affected	Fixed in
Googlegoogle/chrome`pkg:deb/google/chrome`Other threats	Affected <140.0.7339.80	Fixed in 140.0.7339.80

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all Google Chrome installations to version 140.0.7339.80 or later as soon as possible to ensure the vulnerability is patched. 2. Restrict local access to systems running vulnerable Chrome versions by enforcing strict physical security and user access controls. 3. Limit access to debug logs by configuring logging settings to avoid storing sensitive Passkey information or by securing log files with appropriate permissions. 4. Implement endpoint detection and response (EDR) solutions to monitor for suspicious local activity that could indicate attempts to access debug logs or exploit the vulnerability. 5. Educate users and administrators about the risks of local access vulnerabilities and the importance of maintaining updated software. 6. Review and harden authentication workflows involving Passkeys to detect anomalies potentially stemming from leaked credentials. 7. Conduct regular audits of local system access and log file permissions to ensure compliance with security policies. 8. Consider deploying application whitelisting and privilege management to reduce the risk of unauthorized local code execution that could exploit this vulnerability.

Description

Inappropriate implementation in Passkeys in Google Chrome prior to 140.0.7339.80 allowed a local attacker to obtain potentially sensitive information via debug logs. (Chromium security severity: Low)

Impact

For European organizations, the primary impact of CVE-2025-12910 is the potential leakage of sensitive authentication information through debug logs accessible to local attackers. This could lead to unauthorized access if attackers leverage the exposed data to impersonate users or bypass authentication mechanisms. Organizations with shared or poorly secured workstations, or environments where local access controls are lax, are at higher risk. The vulnerability does not directly affect system integrity or availability, but the confidentiality breach could facilitate subsequent attacks, including lateral movement or privilege escalation. Sectors with high security requirements, such as finance, government, and critical infrastructure, may face increased risk due to the sensitivity of the data potentially exposed. Additionally, organizations relying heavily on Chrome for authentication workflows using Passkeys must prioritize remediation to prevent exploitation. Since exploitation requires local access, remote attackers are less likely to benefit directly, but insider threats or malware with local execution capabilities remain concerns. The absence of known exploits reduces immediate risk but does not eliminate the need for prompt mitigation.

CWE-1295Debug Messages Revealing Unnecessary Information (opens in a new tab)
Base weakness
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
Implementation
Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (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 15 Nov 2025, 00:22 UTC

WeaknessesCWE-1295

Technical details

References

Community reviews

Related threats