CVE-2025-11206VulnerabilityPublished 6 Nov 2025Updated 26 Feb 2026

CVE-2025-11206: Google Chrome · Heap buffer overflow

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 7.1 High : upgrade to 141.0.7390.54 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

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 141.0.7390.54

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
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: 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: 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: 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 6 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-25.

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

Affected software

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

AI-suggested

To mitigate CVE-2025-11206, organizations should immediately update Google Chrome to version 141.0.7390.54 or later, where the vulnerability is patched. Beyond patching, organizations should implement network-level protections such as web filtering to block access to untrusted or suspicious websites that could host malicious HTML content. Employing endpoint detection and response (EDR) solutions can help detect anomalous behaviors indicative of sandbox escapes or code execution attempts. Administrators should enforce the principle of least privilege for user accounts to limit the impact of any successful exploit. Additionally, disabling or restricting video playback features in Chrome via group policies or browser configurations can reduce the attack surface if immediate patching is not feasible. Regularly monitoring threat intelligence feeds for any emerging exploits related to this CVE is also recommended. Finally, educating users about the risks of visiting untrusted websites and the importance of prompt browser updates will help reduce exploitation likelihood.

Description

Heap buffer overflow in Video in Google Chrome prior to 141.0.7390.54 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Impact

The primary impact of CVE-2025-11206 is the potential for a remote attacker to escape the Chrome sandbox, which is a critical security boundary. Successful exploitation could allow attackers to execute arbitrary code on the host system with the privileges of the user running Chrome. This can lead to unauthorized access to sensitive data, modification or corruption of data, and disruption of system availability. Organizations relying heavily on Chrome for web access, especially those handling sensitive or classified information, face increased risk of data breaches and system compromise. The vulnerability's remote nature and low complexity make it attractive for attackers to exploit, particularly in targeted attacks or drive-by download scenarios. Although no known exploits are currently in the wild, the publication of this vulnerability may prompt attackers to develop exploits rapidly. The impact extends across all sectors using Chrome, including government, finance, healthcare, and critical infrastructure, potentially leading to significant operational and reputational damage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 22:12 UTC

Technical details

References

Community reviews

Related threats