CVE-2026-7914: Google Chrome · Type Confusion
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 148.0.7778.96 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% 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:H/PR:N/UI:R/S:C/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 29 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
The vendor has released a stable channel update for Chrome around the time of disclosure. Users should update to version 148.0.7778.96 or later to mitigate this vulnerability. Patch status is not explicitly confirmed in the provided advisory, so users should verify the update details on the official Google Chrome Releases blog to ensure the fix is applied.
Description
CVE-2026-7914 is a high-severity type confusion vulnerability in the Accessibility component of Google Chrome on Windows versions prior to 148.0.7778.96. This flaw could allow a remote attacker who has compromised the renderer process to potentially escape the browser's sandbox by using a specially crafted HTML page. The vulnerability affects Chrome desktop on Windows and has a CVSS score of 8.3, indicating a significant risk. No known exploits in the wild have been reported at this time. The vendor advisory linked corresponds to a stable channel update that presumably addresses this issue, but explicit patch confirmation is not provided in the input data.