CVE-2026-5292: Google Chrome · Out-of-bounds Read
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 146.0.7680.178 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 146.0.7680.178
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 1 Apr 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 146.0.7680.178.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Users and administrators should update Google Chrome to version 146.0.7680.178 or later to remediate this vulnerability. Since this is an official fix released by the vendor, applying the update fully mitigates the risk. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-5292 is a high-severity vulnerability in Google Chrome prior to version 146.0.7680.178. It involves an out of bounds read in the WebCodecs component, which can be triggered by a remote attacker via a crafted HTML page. This vulnerability allows unauthorized reading of memory outside the intended bounds, potentially leading to exposure of sensitive information. The vulnerability has a CVSS score of 8.8, indicating a critical impact on confidentiality, integrity, and availability. There are no known exploits in the wild at this time. The issue is fixed in Chrome version 146.