CVE-2023-6702: Google Chrome · Type Confusion
Affects Google ChromeSource CVE Database V5
Not known to be exploited · 44% EPSS · CVSS 8.8 High : upgrade to 120.0.6099.109 soon.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 44.2% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 120.0.6099.109
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Dec 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.
What to do
Upgrade ubuntu/google-chrome-stable and fedora/google-chrome to 120.0.6099.109.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntuubuntu/google-chrome-stablepkg:deb/ubuntu/google-chrome-stableOther threats | Affected
| Fixed in
|
Fedorafedora/google-chromepkg:rpm/fedora/google-chromeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate update of all Google Chrome installations to version 120.0.6099.109 or later to apply the official patch. 2. Enforce enterprise browser update policies to ensure timely deployment of security patches. 3. Implement web filtering solutions to block access to known malicious or suspicious websites that could host exploit payloads. 4. Educate users about the risks of clicking unknown links or visiting untrusted websites to reduce the likelihood of successful social engineering. 5. Deploy endpoint detection and response (EDR) tools capable of detecting anomalous browser behavior indicative of exploitation attempts. 6. Use browser sandboxing and isolation technologies to limit the impact of potential exploitation. 7. Monitor network traffic for unusual outbound connections that may indicate post-exploitation activity. 8. Regularly review and audit browser extensions and plugins to minimize attack surface. 9. Coordinate with IT and security teams to ensure rapid incident response capability in case of exploitation. 10. Consider deploying multi-factor authentication and network segmentation to limit lateral movement if a compromise occurs.
Description
Type confusion in V8 in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
References
- chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop_12.html (opens in a new tab)
- crbug.com/1501326 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6NWZ23ZJ62XKWVNGHSIZQYILVJWH5BLI/ (opens in a new tab)
- security.gentoo.org/glsa/202401-34 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZGJ732QHS2FAYF62RFF3YP4VIQY75K7V/ (opens in a new tab)