Skip to main content
VulnerabilityPublished Updated

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

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 138.0.7204.157 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.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 138.0.7204.157
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Google Chrome to 138.0.7204.157.

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =138.0.7204.157
  • <138.0.7204.157
Fixed in
  • 138.0.7204.157

AI-suggested

To mitigate CVE-2025-7657, organizations should immediately update all Chrome installations to version 138.0.7204.157 or later, where the vulnerability is patched. Beyond patching, network-level defenses should be employed to block access to known malicious websites and filter suspicious WebRTC traffic. Security teams should configure browser policies to restrict or disable WebRTC where not needed, reducing the attack surface. Employing endpoint detection and response (EDR) solutions to monitor for anomalous browser behavior or heap corruption indicators can aid in early detection. User education is critical to avoid interacting with untrusted links or websites. Additionally, organizations should maintain up-to-date threat intelligence feeds to identify emerging exploits targeting this vulnerability. For high-security environments, consider isolating browser processes or using sandboxing technologies to limit potential damage from exploitation.

Description

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

References

Community reviews

Loading reviews…