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

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

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.1 High : upgrade to 141.0.7390.65 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 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

Upgrade Google Chrome to 141.0.7390.65.

Affected software

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

AI-suggested

Organizations and users should immediately update Google Chrome to version 141.0.7390.65 or later, where this vulnerability is patched. Beyond patching, implementing network-level protections such as web filtering to block access to known malicious sites can reduce exposure. User education is critical to prevent clicking on suspicious links or visiting untrusted websites that could host crafted HTML pages exploiting this flaw. Employing endpoint detection and response (EDR) tools to monitor for unusual browser memory access patterns or crashes may help detect exploitation attempts. Administrators should review browser sync settings and consider limiting synchronization of sensitive data until patches are applied. For enterprise environments, deploying browser security policies that restrict extensions and scripts can reduce attack surface. Regular vulnerability scanning and threat intelligence updates will assist in early detection of emerging exploits related to this vulnerability. Finally, maintaining a robust incident response plan will enable rapid containment if exploitation is detected.

Description

Heap buffer overflow in Sync in Google Chrome prior to 141.0.7390.65 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)

Impact

The primary impact of CVE-2025-11458 is on the confidentiality and integrity of user data within Google Chrome. Successful exploitation can lead to unauthorized disclosure of sensitive information stored in memory, such as user credentials, session tokens, or synced data. This can facilitate further attacks like account takeover or data leakage. The integrity of the browser's operation may also be compromised, potentially allowing attackers to manipulate browser behavior or bypass security controls. Since the vulnerability does not affect availability, denial-of-service is not a direct concern. However, the widespread use of Chrome globally means that millions of users and organizations are potentially exposed. Enterprises relying on Chrome for secure browsing and data synchronization face risks of data breaches and loss of trust. The requirement for user interaction (visiting a malicious page) somewhat limits automated exploitation but does not eliminate risk, especially in environments where phishing or drive-by download attacks are common. The absence of known exploits in the wild currently reduces immediate threat but does not preclude future active exploitation campaigns.

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