VulnerabilityPublished 2 Dec 2025

CVE-2025-13632: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 143.0.7499.41 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

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

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: 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: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 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 143.0.7499.41.

Affected software

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

AI-suggested

Update Google Chrome to version 143.0.7499.41 or later immediately to apply the fix for this vulnerability.
Implement group policies or enterprise management tools to restrict or control the installation of Chrome extensions, allowing only trusted extensions from verified sources.
Educate users about the risks of installing browser extensions from untrusted sources and train them to recognize phishing or social engineering attempts that may lead to malicious extension installation.
Monitor browser extension activity and audit installed extensions regularly to detect unauthorized or suspicious extensions.
Employ endpoint detection and response (EDR) solutions to identify unusual behaviors indicative of sandbox escape attempts or privilege escalation.
Consider deploying application control policies that limit execution of unauthorized code outside the browser sandbox.
Maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.

Description

Inappropriate implementation in DevTools in Google Chrome prior to 143.0.7499.41 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (Chromium security severity: High)

Impact

For European organizations, this vulnerability poses a moderate risk primarily because Google Chrome is one of the most widely used browsers in Europe, both in enterprise and consumer contexts. A successful sandbox escape could allow attackers to execute code with elevated privileges on the host system, potentially leading to data leakage or disruption of services. Confidentiality could be compromised if sensitive information accessible via the browser or local system is exposed. Availability impacts could arise if the attacker disrupts browser or system operations. The requirement for user interaction (installing a malicious extension) reduces the likelihood of widespread automated exploitation but does not eliminate risk, especially in environments where users may be targeted via phishing or social engineering. Organizations handling sensitive data, such as financial institutions, healthcare providers, and government agencies, are at higher risk. The absence of known exploits in the wild currently reduces immediate threat but patching is critical to prevent future attacks.

CWE-194Unexpected Sign Extension (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses.
Implementation
Avoid using signed variables if you don't need to represent negative values. When negative values are needed, perform validation after you save those values to larger data types, or before passing them to functions that are expecting unsigned values.
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 9 Dec 2025, 20:16 UTC

WeaknessesCWE-194

Technical details

References

Community reviews

Related threats