CVE-2023-6347: Google Chrome · Use After Free
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 119.0.6045.199 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 119.0.6045.199
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 29 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 26 Oct 2026.
What to do
Upgrade the to 119.0.6045.199.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Debiandebian/google-chromepkg:deb/debian/google-chromeOther 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
European organizations should prioritize immediate patching by upgrading all instances of Google Chrome to version 119.0.6045.199 or later. Beyond patching, organizations should implement network-level protections such as web filtering to block access to known malicious sites and employ endpoint detection and response (EDR) solutions capable of detecting anomalous browser behavior indicative of exploitation attempts. User education campaigns should be conducted to raise awareness about the risks of clicking on unknown links or visiting untrusted websites. Additionally, deploying browser isolation technologies can help contain potential exploitation by executing web content in a sandboxed environment. Organizations should also ensure that their incident response teams are prepared to detect and respond to exploitation attempts, including monitoring for unusual process behavior or memory corruption indicators. Regular vulnerability scanning and asset inventory management will help identify and remediate outdated browser versions promptly. Finally, leveraging multi-factor authentication and network segmentation can limit the impact of a successful compromise.
Description
Use after free in Mojo in Google Chrome prior to 119.0.6045.199 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
References
- chromereleases.googleblog.com/2023/11/stable-channel-update-for-desktop_28.html (opens in a new tab)
- crbug.com/1494461 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJROPNKWW65R34J4IYGTJ7A3OBPUL4IQ/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6T7ABNYMOI4ZHVCSPCNP7HQTOLGF53A2/ (opens in a new tab)
- debian.org/security/2023/dsa-5569 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C7XQNYZZA3X2LBJF57ZHKXWOMJKNLZYR/ (opens in a new tab)
- security.gentoo.org/glsa/202401-34 (opens in a new tab)