VulnerabilityPublished 10 Sep 2025Updated 26 Feb 2026

CVE-2025-10200: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High · fixed in 140.0.7339.127 : patch Google Chrome soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

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

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

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 10 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 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

Affected software

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

AI-suggested

To mitigate CVE-2025-10200, organizations should immediately update all instances of Google Chrome on desktop platforms to version 140.0.7339.127 or later, where the vulnerability is patched. Automated update mechanisms should be verified and enforced to ensure timely deployment. Where immediate patching is not feasible, temporarily disabling ServiceWorkers via browser settings or enterprise policies can reduce exposure, though this may impact functionality. Employing browser security features such as site isolation, strict content security policies (CSP), and disabling JavaScript on untrusted sites can further reduce risk. Network-level defenses like web filtering and intrusion prevention systems should be tuned to detect and block known malicious payloads targeting this vulnerability. User education to avoid clicking on suspicious links or visiting untrusted websites is critical since exploitation requires user interaction. Monitoring browser crash reports and unusual network activity can help detect attempted exploitation. Finally, organizations should maintain an inventory of browser versions in use and integrate vulnerability management processes to rapidly respond to such critical flaws in widely used software.

Description

Use after free in Serviceworker in Google Chrome on Desktop prior to 140.0.7339.127 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

Impact

The impact of CVE-2025-10200 is substantial for organizations worldwide due to the widespread use of Google Chrome as a primary web browser. Successful exploitation can lead to remote code execution, allowing attackers to run arbitrary code in the context of the browser process. This can result in full system compromise, data theft, installation of malware, or disruption of services. Confidentiality is at risk as attackers may access sensitive information processed or stored by the browser. Integrity can be compromised through unauthorized code execution or manipulation of web content. Availability may be affected if attackers cause crashes or denial of service conditions. The vulnerability's network attack vector and lack of required privileges make it a prime target for phishing campaigns or drive-by downloads. Enterprises relying on Chrome for web applications, especially those using ServiceWorkers for offline or push functionality, face increased risk. The absence of known exploits in the wild currently reduces immediate threat but does not diminish the urgency of patching. Failure to address this vulnerability could lead to significant operational and reputational damage, particularly in sectors handling sensitive data such as finance, healthcare, and government.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats