VulnerabilityPublished 3 Dec 2025

CVE-2025-13992: Google Chrome · Side-channel Information Leakage

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium · fixed in 139.0.7258.66 : update Google Chrome when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.7Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 139.0.7258.66

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 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 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

Affected software

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

AI-suggested

The primary mitigation is to update Google Chrome to version 139.0.7258.66 or later, where the vulnerability is patched. Organizations should enforce automatic browser updates or centrally manage Chrome deployments to ensure timely patching. Implementing strict Content Security Policies (CSP) can reduce the risk of malicious HTML content executing side-channel attacks. Employ browser isolation technologies or sandboxing to add layers of defense. Educate users about the risks of interacting with untrusted websites and phishing attempts, as exploitation requires user interaction. Monitor network traffic and browser behavior for anomalies that may indicate exploitation attempts. For high-security environments, consider using hardened browser configurations or alternative browsers with different isolation models until patches are applied. Regularly review and update security policies to incorporate emerging browser vulnerabilities and side-channel attack mitigations.

Description

CVE-2025-13992 is a medium-severity side-channel information leakage vulnerability in Google Chrome versions prior to 139.0.7258.66. It allows a remote attacker to bypass site isolation by using a crafted HTML page, potentially leaking sensitive information across site boundaries. Exploitation requires user interaction but no privileges or authentication. The vulnerability impacts confidentiality but not integrity or availability. No known exploits are currently in the wild. European organizations using affected Chrome versions may face risks of cross-site data leakage, especially in sectors relying heavily on browser security. Mitigation involves updating Chrome to version 139.

Impact

For European organizations, this vulnerability poses a risk of cross-site data leakage through compromised browsers, potentially exposing sensitive corporate or personal information. Sectors such as finance, healthcare, and government, which rely heavily on browser-based applications and handle sensitive data, are particularly at risk. The bypass of site isolation could allow attackers to infer confidential data from other sites or sessions, undermining user privacy and organizational security. While the vulnerability does not allow code execution or system compromise, the confidentiality breach could facilitate further targeted attacks or data exfiltration. The requirement for user interaction limits mass exploitation but targeted phishing or watering hole attacks could leverage this flaw. Organizations with remote or hybrid workforces using Chrome browsers need to prioritize patching to prevent exploitation. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop techniques over time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Dec 2025, 20:02 UTC

Technical details

References

Community reviews

Related threats