ChromeWeb browser · Google
CVE-2026-5292
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut of bounds read in WebCodecs in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds read vulnerability exists in the WebCodecs API of Google Chrome versions prior to 146.0.7680.178. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing the attacker to read memory contents outside the intended buffer bounds.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 146.0.7680.177CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help in the Chrome address bar, or use 'Google Chrome > About Google Chrome' from the application menu. The version number is displayed on the page that opens.Affected if The displayed version is less than 146.0.7680.177 (for example, 146.0.7680.176, 145.x.x.x, etc.)
-
Confirm WebCodecs API availabilityOpen a new tab and type 'chrome://flags/#enable-experimental-web-platform-features' in the address bar. Check the status of the WebCodecs-related flags.Affected if WebCodecs is enabled (the default state). The vulnerability exists regardless of flag settings since WebCodecs is built into Chrome.
-
Verify Chrome channel and update statusNavigate to chrome://settings/help and note if the browser shows 'Update available' or indicates it is on the Stable, Beta, Dev, or Canary channel.Affected if The browser is on Stable channel with version below 146.0.7680.177, or on any older channel (Beta/Dev/Canary) that has not been updated to 146.0.7680.178 or later.
A user is affected if their installed Google Chrome version is below 146.0.7680.177 and the WebCodecs API is accessible (default state).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped146.0.7680.177
Update Google Chrome to version 146.0.7680.178 or later. Organizations should push browser updates through their endpoint management systems and remind users to restart their browsers after updating.
Chrome 146.0.7680.178 or later
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Go to Help > About Google Chrome
- Chrome will automatically check for and install any available updates
- Restart Chrome after the update completes
- Verify the version by returning to Help > About Google Chrome and confirming the version number is 146.0.7680.178 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data