dbcve.org
ChromeWeb browser · Google

CVE-2026-5282

HIGH · 8.1 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 146.0.7680.177 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Out 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: High)

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 confidence

An out-of-bounds read vulnerability exists in the WebCodecs API of Google Chrome prior to version 146.0.7680.178. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing unauthorized memory reads outside allocated buffers.

MitigationUpdate Google Chrome to version 146.0.7680.178 or later to patch the vulnerability. Organizations may also consider deploying browser management tools to ensure end-users have the patched version.

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
Affected:< 146.0.7680.177

CVSS 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Chrome is installed
    Check for Chrome executable in common locations (Windows: %PROGRAMFILES%\Google\Chrome\Application\chrome.exe, macOS: /Applications/Chrome.app, Linux: /usr/bin/google-chrome) or open chrome://version in a browser
    Affected if Chrome browser is present on the system
  2. Determine installed Chrome version
    Navigate to chrome://version in the Chrome browser or run 'chrome --version' from command line. The version string appears as 'Version X.X.X.X'
    Affected if Unable to retrieve version information
  3. Compare version against affected range
    Extract the full version number (four numeric parts) and compare numerically to 146.0.7680.178. Any version less than 146.0.7680.178 is in the affected range
    Affected if Installed version is less than 146.0.7680.178 (for example: 146.0.7680.177, 146.0.7680.50, 145.0.6045.189, etc.)
  4. Identify WebCodecs API usage
    Search application code, browser extensions, or web content for usage of 'VideoDecoder', 'AudioDecoder', 'VideoEncoder', or 'AudioEncoder' WebCodecs interfaces. In Chrome DevTools, check console for WebCodecs API calls
    Affected if Applications or web pages actively use the WebCodecs API to process encoded media data

A user is affected if Chrome with version below 146.0.7680.178 is installed AND any content or application processes encoded media data through the WebCodecs API, enabling potential out-of-bounds memory reads via crafted media files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 146.0.7680.177 or later
Fixed in 146.0.7680.177
Interim mitigation

Update Google Chrome to version 146.0.7680.178 or later to patch the vulnerability. Organizations may also consider deploying browser management tools to ensure end-users have the patched version.

Recommended fix High confidence

Chrome 146.0.7680.178 or later

  1. Open Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current Chrome version number displayed
  3. If the version is below 146.0.7680.178, Chrome will automatically check for and prompt you to install the latest update
  4. Restart Chrome after the update completes

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
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5282 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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