CVE-2025-10502VulnerabilityPublished 24 Sep 2025Updated 26 Feb 2026

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

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

8.8High

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

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

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

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

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

Affected software

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

AI-suggested

To mitigate CVE-2025-10502, organizations should immediately update all affected Chrome browsers to version 140.0.7339.185 or later, where the vulnerability is patched. Beyond patching, network-level defenses can help reduce exposure by filtering or blocking suspicious traffic patterns that may carry exploit payloads targeting the ANGLE component. Implementing browser security policies that restrict or sandbox web content can limit the impact of successful exploitation. User education to recognize phishing attempts and avoid interacting with untrusted links or websites is essential to reduce the risk of triggering the vulnerability. Monitoring browser behavior for anomalies such as unexpected crashes or unusual memory usage can provide early detection of exploitation attempts. Organizations should also consider deploying endpoint detection and response (EDR) solutions capable of identifying exploit techniques targeting browser memory corruption. Regular vulnerability scanning and penetration testing can help ensure that Chrome installations remain up to date and resilient against emerging threats.

Description

Heap buffer overflow in ANGLE in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via malicious network traffic. (Chromium security severity: High)

Impact

The exploitation of CVE-2025-10502 can have severe consequences for organizations worldwide. Successful attacks could lead to arbitrary code execution within the context of the browser, enabling attackers to steal sensitive information, install malware, or pivot to internal networks. The compromise of confidentiality, integrity, and availability can disrupt business operations, lead to data breaches, and damage organizational reputation. Given Chrome's dominant market share globally, a large number of users and enterprises are potentially exposed. Attackers could leverage this vulnerability in targeted attacks or widespread campaigns to compromise endpoints, especially in environments where patching is delayed. The requirement for user interaction limits automated exploitation but does not eliminate risk, as phishing and social engineering remain effective vectors. The vulnerability is particularly critical for sectors relying heavily on web applications and remote browsing, such as finance, government, and critical infrastructure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats