CVE-2024-0808: Google Chrome · Integer underflow
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 121.0.6167.85 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 121.0.6167.85
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Jan 2024
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-25.
What to do
Upgrade ubuntu/chrome to 121.0.6167.85.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntuubuntu/chromepkg:deb/ubuntu/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 updating Google Chrome to version 121.0.6167.85 or later, where this vulnerability is patched. Given the critical severity and ease of exploitation, automated patch management systems should be leveraged to ensure rapid deployment across all endpoints. Network-level protections such as web filtering and sandboxing of untrusted files can reduce exposure to malicious payloads exploiting this vulnerability. Endpoint detection and response (EDR) solutions should be tuned to detect anomalous heap corruption or exploitation attempts related to Chrome processes. Organizations should also educate users about the risks of opening untrusted files or links, although user interaction is not required for exploitation. For environments where immediate patching is not feasible, temporarily disabling or restricting access to the WebUI features in Chrome, if possible, may reduce risk. Continuous monitoring of threat intelligence feeds for emerging exploit reports related to CVE-2024-0808 is recommended to adapt defenses promptly.
Description
Integer underflow in WebUI in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
References
- chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html (opens in a new tab)
- crbug.com/1504936 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VXDSGAFQD4BDB4IB2O4ZUSHC3JCVQEKC/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MMI6GXFONZV6HE3BPZO3AP6GUVQLG4JQ/ (opens in a new tab)