CVE-2025-13640VulnerabilityPublished 2 Dec 2025

CVE-2025-13640: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.5Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: 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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 2 Dec 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

Affected software

Product	Affected	Fixed in
Google Chrome	Affected =143.0.7499.41	Fixed in–

AI-suggested

To mitigate CVE-2025-13640, European organizations should immediately update all Chrome installations to version 143.0.7499.41 or later, where the vulnerability is fixed. Beyond patching, organizations should enforce strict physical security controls to prevent unauthorized access to devices, including secure storage, device encryption, and endpoint lockdown policies. Implementing multi-factor authentication (MFA) for accessing sensitive applications can reduce the impact of stolen credentials. Additionally, organizations should consider disabling password saving features in browsers on high-risk or shared devices and encourage the use of dedicated password managers with stronger security controls. Regular audits of device inventory and access logs can help detect potential physical compromise. User training on the risks of leaving devices unattended and the importance of locking screens can further reduce exposure. Finally, integrating endpoint detection and response (EDR) solutions can help identify suspicious local activities indicative of exploitation attempts.

Description

Inappropriate implementation in Passwords in Google Chrome prior to 143.0.7499.41 allowed a local attacker to bypass authentication via physical access to the device. (Chromium security severity: Low)

Impact

For European organizations, the primary impact of CVE-2025-13640 is the potential unauthorized access to stored passwords on devices running vulnerable Chrome versions if an attacker gains physical access. This could lead to credential theft, unauthorized access to corporate resources, and potential lateral movement within networks. While the vulnerability does not enable remote exploitation, the risk is significant in environments where devices are shared, lost, or stolen, such as in mobile workforces or public-facing terminals. The breach of stored credentials could compromise user accounts, internal systems, and sensitive data, undermining confidentiality and integrity. Given the widespread use of Chrome across European enterprises and public sector organizations, especially in countries with high Chrome market share, this vulnerability could have a broad impact if not addressed. However, the requirement for physical access and the low severity rating reduce the likelihood of widespread exploitation. Nonetheless, organizations with high-value targets or sensitive data should treat this vulnerability seriously to prevent insider threats or opportunistic attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Dec 2025, 19:23 UTC

Technical details

References

Community reviews

Related threats