Skip to main content
VulnerabilityPublished Updated

CVE-2025-1916: 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.35 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 134.0.6998.35
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 5 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 26 Oct 2026.

What to do

Upgrade Google Chrome to 134.0.6998.35.

Affected software

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

AI-suggested

To mitigate CVE-2025-1916, organizations and users should immediately update Google Chrome to version 134.0.6998.35 or later, where the vulnerability is patched. Beyond patching, organizations should enforce strict extension policies, allowing installation only from trusted sources or via enterprise-managed extension whitelists to reduce the risk of malicious extension installation. User education on the risks of installing untrusted extensions and recognizing social engineering attempts is critical. Implement browser security features such as sandboxing and enable Chrome’s built-in security protections like site isolation and strict content security policies. Network-level controls can also help by blocking access to known malicious sites hosting crafted HTML pages. Regularly audit installed extensions and remove any that are unnecessary or suspicious. Monitoring browser behavior for anomalies can provide early detection of exploitation attempts. Finally, maintain an incident response plan to quickly address any suspected compromise stemming from browser vulnerabilities.

Description

Use after free in Profiles in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

References

Community reviews

Loading reviews…