Skip to main content
CVE-2025-2136VulnerabilityPublished Updated

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

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 134.0.6998.88 soon.

Data as of 26 Oct 2026, 06:26 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 134.0.6998.88
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 10 Mar 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 2026-10-26.

What to do

Upgrade Google Chrome to 134.0.6998.88.

Affected software

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

AI-suggested

To mitigate CVE-2025-2136, organizations should immediately plan to update Google Chrome to version 134.0.6998.88 or later once the patch is available. Until then, consider the following specific measures: 1) Disable or restrict access to the Chrome Inspector and developer tools in managed environments to reduce attack surface. 2) Employ browser security features such as sandboxing, site isolation, and strict content security policies to limit the impact of malicious web content. 3) Use network-level protections like web filtering and intrusion prevention systems to block access to known malicious URLs and suspicious HTML content. 4) Educate users about the risks of visiting untrusted websites and clicking on unknown links to reduce the likelihood of user interaction with malicious pages. 5) Monitor browser behavior and system logs for anomalies indicative of exploitation attempts, including unexpected crashes or memory errors. 6) Implement endpoint detection and response (EDR) solutions capable of identifying exploitation techniques related to heap corruption and use-after-free vulnerabilities. 7) Maintain an inventory of Chrome versions deployed across the organization to ensure timely patch management. These targeted actions complement standard patching and help reduce exposure during the window before updates are applied.

Description

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

References

Community reviews

Loading reviews…