VulnerabilityPublished 6 Nov 2025

CVE-2025-11215: Google Chrome · Off by One Error

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 141.0.7390.54 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
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: 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: None: There is no impact to availability within 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 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 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-11215, European organizations should enforce rapid deployment of Chrome updates to version 141.0.7390.54 or later, where the vulnerability is fixed. Automated update mechanisms should be enabled and monitored to ensure compliance across all endpoints. Network-level protections such as web filtering and URL reputation services can help block access to known malicious sites that might exploit this vulnerability. Security awareness training should emphasize the risks of visiting untrusted websites and recognizing phishing attempts that could lead to exploitation. Endpoint detection and response (EDR) tools can be configured to monitor for unusual browser behaviors indicative of exploitation attempts. Additionally, organizations should consider isolating high-risk browsing activities using sandboxing or dedicated browsing environments to limit potential exposure. Regular vulnerability scanning and penetration testing should include checks for outdated browser versions. Finally, incident response plans should be updated to address potential information disclosure incidents stemming from browser vulnerabilities.

Description

Off by one error in V8 in Google Chrome prior to 141.0.7390.54 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)

Impact

For European organizations, the primary impact of CVE-2025-11215 is the potential exposure of sensitive information through out-of-bounds memory reads in the Chrome browser. This can lead to leakage of confidential data such as authentication tokens, session cookies, or other in-memory secrets, which could be leveraged in subsequent attacks like session hijacking or targeted phishing. Although the vulnerability does not allow code execution or system compromise directly, the confidentiality breach can undermine trust and lead to data breaches. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, may face compliance risks if sensitive data is exposed. The requirement for user interaction means that phishing or social engineering campaigns could be used to lure users to malicious sites. The widespread use of Chrome in Europe, including in critical infrastructure and enterprise environments, increases the potential attack surface. However, the medium severity and lack of known exploits reduce the immediate threat level, though vigilance and timely patching remain essential.

CWE-193Off-by-one Error (opens in a new tab)
Base weakness
A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.
Implementation
When copying character arrays or using character manipulation methods, the correct size parameter must be used to account for the null terminator that needs to be added at the end of the array.
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 14 Nov 2025, 00:49 UTC

WeaknessesCWE-193

Technical details

References

Community reviews

Related threats