Skip to main content
VulnerabilityPublished Updated

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

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 141.0.7390.65 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.3% chance of exploitation in 30 days – higher than 26% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 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 141.0.7390.65.

Affected software

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

AI-suggested

To mitigate CVE-2025-11460, organizations should immediately update all instances of Google Chrome to version 141.0.7390.65 or later, where the vulnerability is patched. Beyond patching, organizations should implement strict content filtering to block or scan untrusted video files before they reach end users. Employing endpoint protection solutions capable of detecting anomalous behavior related to memory corruption can help identify exploitation attempts. User education is critical to reduce the risk of social engineering attacks that trick users into opening malicious media. Disabling or restricting automatic media playback in browsers can reduce exposure. Network segmentation and least privilege principles should be enforced to limit the impact of a potential breach. Monitoring browser logs and network traffic for unusual activity related to video file handling can provide early warning signs. Finally, maintaining a robust incident response plan ensures rapid containment if exploitation occurs.

Description

Use after free in Storage in Google Chrome prior to 141.0.7390.65 allowed a remote attacker to execute arbitrary code via a crafted video file. (Chromium security severity: High)

References

Community reviews

Loading reviews…