CVE-2026-5282: Google Chrome · Out-of-bounds Read
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 146.0.7680.178 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% 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:N/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 Chrome and google/chrome to 146.0.7680.178.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
Googlegoogle/chromepkg:deb/google/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
A fixed version of Google Chrome (146.0.7680.178 or later) addresses this vulnerability. Users and administrators should update to this version or later to remediate the issue. Since this is not a cloud service, patching the client software is required. Patch status is not explicitly confirmed in vendor advisory content, so verify with official Google Chrome security updates for the latest remediation guidance.
Description
CVE-2026-5282 is a high-severity vulnerability in Google Chrome's WebCodecs component prior to version 146.0.7680.178. It allows a remote attacker to perform an out of bounds memory read by crafting a malicious HTML page. This vulnerability can lead to information disclosure and potentially impact the availability of the browser. The issue is categorized as CWE-125 (Out-of-bounds Read).