CVE-2023-5997VulnerabilityPublished 15 Nov 2023Updated 16 Dec 2025

CVE-2023-5997: Google Chrome · Use after free

Affects Google ChromeSource CVE Database V5

Not known to be exploited : upgrade to 119.0.6045.159 soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated High by the CNA (Chrome) · No CVSS score from NVD or the CNA

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 119.0.6045.159

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade debian/chrome and fedora/chrome and gentoo/chrome to 119.0.6045.159.

Affected software

Product	Affected	Fixed in
Debiandebian/chrome`pkg:deb/debian/chrome`Other threats	Affected <119.0.6045.159	Fixed in 119.0.6045.159
Fedorafedora/chrome`pkg:rpm/fedora/chrome`Other threats	Affected <119.0.6045.159	Fixed in 119.0.6045.159
Gentoogentoo/chrome`pkg:rpm/gentoo/chrome`Other threats	Affected <119.0.6045.159	Fixed in 119.0.6045.159

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

AI-suggested

Organizations should immediately ensure all instances of Google Chrome are updated to version 119.0.6045.159 or later, as this version contains the patch for CVE-2023-5997. Beyond patching, organizations should implement browser security best practices such as enabling sandboxing features, using browser isolation technologies, and restricting the execution of untrusted web content through content security policies. Employing endpoint detection and response (EDR) solutions can help detect anomalous browser behavior indicative of exploitation attempts. Network-level protections like web filtering and intrusion prevention systems should be configured to block access to known malicious sites. User awareness training should emphasize the risks of visiting untrusted websites and the importance of timely software updates. For high-security environments, consider deploying hardened browser configurations or alternative browsers with reduced attack surfaces. Continuous monitoring for unusual browser crashes or memory corruption events can provide early warning of exploitation attempts.

Description

CVE-2023-5997 is a use-after-free vulnerability in the garbage collection mechanism of Google Chrome versions prior to 119.0.6045.159. This flaw allows a remote attacker to trigger heap corruption by crafting a malicious HTML page, potentially leading to arbitrary code execution or browser compromise. Exploitation does not require user authentication but does require user interaction to visit a malicious webpage. No known exploits are currently in the wild. The vulnerability affects a widely used browser, making it a significant risk for European organizations relying on Chrome for web access. Timely patching is critical to prevent exploitation. The severity is assessed as high due to the potential impact on confidentiality, integrity, and availability, combined with the ease of exploitation via web content.

Impact

For European organizations, the impact of CVE-2023-5997 is considerable due to the widespread use of Google Chrome across enterprises, government agencies, and critical infrastructure sectors. Successful exploitation could lead to arbitrary code execution within the browser context, enabling attackers to bypass security controls, access sensitive corporate data, or deploy further malware. This could compromise confidentiality by exposing private information, integrity by allowing unauthorized code execution, and availability if the browser or system is destabilized. Given that Chrome is often used to access web-based applications and services, exploitation could serve as an entry point for broader network compromise. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, as attackers may develop exploits rapidly following public disclosure. European organizations with high reliance on Chrome for daily operations, especially those in finance, healthcare, and government sectors, face elevated risk. Additionally, the vulnerability could be leveraged in targeted attacks against high-value individuals or entities within Europe.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Dec 2025, 18:34 UTC

Technical details

References

Community reviews

Related threats