CVE-2026-9983: Google Chrome · Type Confusion
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 148.0.7778.216 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 148.0.7778.216
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 28 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.216.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Google has released an official stable channel update for Chrome version 148.0.7778.216 that addresses this vulnerability. Users and administrators should update to this version or later to remediate the issue. Patch status is confirmed by the vendor advisory. No additional mitigation steps are specified beyond applying the update.
Description
CVE-2026-9983 is a high-severity type confusion vulnerability in the Skia component of Google Chrome prior to version 148.0.7778.216. This flaw allows a remote attacker to execute arbitrary code within the browser's sandbox by tricking the user into visiting a crafted HTML page. The vulnerability has a CVSS score of 8.8, indicating a significant risk to confidentiality, integrity, and availability. There are no known exploits in the wild at this time. Google has published a stable channel update addressing this issue in Chrome version 148.0.