CVE-2026-7896: Google Chrome · Integer Overflow
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 148.0.7778.96 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 148.0.7778.96
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 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade Google Chrome to 148.0.7778.96.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Google has released a stable channel update for Chrome that fixes this vulnerability. Users and administrators should update their Chrome browsers to version 148.0.7778.96 or later to mitigate this issue. Patch status is confirmed by the vendor advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html.
Description
CVE-2026-7896 is a high-severity integer overflow vulnerability in the Blink component of Google Chrome prior to version 148.0.7778.96. This flaw could allow a remote attacker to cause heap corruption by crafting a malicious HTML page, potentially leading to code execution or browser compromise. The vulnerability has a CVSS score of 8.8, indicating significant impact on confidentiality, integrity, and availability. There are no known exploits in the wild at this time. The vendor advisory linked corresponds to a Chrome stable channel update addressing this issue.