Skip to main content
CVE-2024-1077VulnerabilityPublished Updated

CVE-2024-1077: Google Chrome · Use after free

Affects Google ChromeSource CVE Database V5

0

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

Data as of 25 Oct 2026, 19:02 UTC

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

  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-25.

What to do

Upgrade google/chrome to 121.0.6167.139.

Affected software

ProductAffectedFixed in
Googlegoogle/chromepkg:deb/google/chromeOther threatsAffected
  • <121.0.6167.139
Fixed in
  • 121.0.6167.139

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should prioritize immediate updating of all Google Chrome installations to version 121.0.6167.139 or later. Beyond patching, organizations should implement strict email and web filtering to block malicious files and links that could trigger exploitation. User awareness training should emphasize caution when opening unexpected or suspicious files, especially from unknown sources. Network segmentation and endpoint detection and response (EDR) solutions can help detect and contain exploitation attempts. Additionally, organizations should enforce the use of browser security features such as sandboxing, site isolation, and strict content security policies to reduce the attack surface. Regular vulnerability scanning and asset inventory management will ensure that no outdated Chrome versions remain in use. Finally, incident response plans should be updated to include scenarios involving browser-based exploitation.

Description

Use after free in Network in Google Chrome prior to 121.0.6167.139 allowed a remote attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)

References

Community reviews

Loading reviews…