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

CVE-2025-10501: Google Chrome · Use after free

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.8High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% 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-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

Affected software

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

AI-suggested

To effectively mitigate CVE-2025-10501, organizations should implement the following specific measures: 1) Immediately update Google Chrome to version 140.0.7339.185 or later, where the vulnerability is patched. 2) Employ enterprise browser management tools to enforce automatic updates and prevent use of outdated versions. 3) Restrict or monitor WebRTC usage in environments where it is not essential, using browser policies or network-level controls to limit exposure. 4) Deploy web content filtering and URL reputation services to block access to known malicious sites that could host exploit pages. 5) Educate users about the risks of visiting untrusted websites and the importance of applying browser updates promptly. 6) Consider using browser sandboxing or isolation technologies to contain potential exploitation impacts. 7) Monitor security advisories and threat intelligence feeds for any emerging exploit activity related to this vulnerability. These targeted actions go beyond generic patching advice by focusing on controlling WebRTC exposure and enhancing organizational update policies.

Description

Use after free in WebRTC in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Impact

The exploitation of CVE-2025-10501 can lead to severe consequences for organizations and individual users worldwide. Successful exploitation allows remote attackers to execute arbitrary code within the browser context, potentially leading to full system compromise if sandbox escapes are chained. This threatens the confidentiality of sensitive data accessed via the browser, the integrity of system and application processes, and the availability of services due to potential crashes or denial-of-service conditions. Organizations relying on Chrome for web-based communications, especially those using WebRTC for conferencing, telephony, or real-time data exchange, face increased risk of targeted attacks or widespread exploitation. The vulnerability could be leveraged for espionage, data theft, or disruption of critical business operations. Given Chrome's dominant market share globally, the scope of impact is extensive, affecting enterprises, governments, and consumers alike. The requirement for user interaction (visiting a malicious webpage) lowers the barrier for exploitation but also provides an opportunity for mitigation through user awareness and technical controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats