dbcve.org
ChromeWeb browser · Google

CVE-2026-8529

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 148.0.7778.168 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Heap buffer overflow in Codecs in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted video file. (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

Heap buffer overflow vulnerability in Google Chrome's Codecs component allows remote code execution via specially crafted video files. The flaw exists in versions prior to 148.0.7778.168 and enables attackers to escape the sandbox through malformed media content.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later to remediate this vulnerability. Exercise caution with untrusted video files until the update is applied.

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:< 148.0.7778.168

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
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 checks

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

  1. Check if Google Chrome is installed
    On Windows, check for Chrome in Program Files or Program Files (x86). On macOS, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or 'which chromium-browser'.
    Affected if Chrome is not found on the system, the system is not affected by this specific Chrome vulnerability.
  2. Retrieve installed Chrome version
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome. Alternatively, on Windows check the version in the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome\DisplayVersion. On macOS, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString'. On Linux, run 'google-chrome --version' or 'chromium-browser --version'.
    Affected if Unable to determine the installed version, further investigation is needed.
  3. Compare version against affected range
    Compare the installed version number to 148.0.7778.168. Note that version comparison must be done numerically (e.g., 148.0.7778.100 is less than 148.0.7778.168).
    Affected if The installed version is a four-part number less than 148.0.7778.168 (e.g., 147.0.6095.115, 148.0.7778.100, etc.).
  4. Verify Codecs component is enabled
    In Chrome, go to chrome://components and verify that the 'Widevine Content Decryption Module' or other codec components are present. This is a default component for video playback and cannot be easily disabled.
    Affected if Codecs are disabled or removed, the exploit surface is reduced but the underlying vulnerable code may still exist in the binary.

The environment is affected if Google Chrome is installed with a version number lower than 148.0.7778.168.

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 148.0.7778.168 or later
Fixed in 148.0.7778.168
Interim mitigation

Update Google Chrome to version 148.0.7778.168 or later to remediate this vulnerability. Exercise caution with untrusted video files until the update is applied.

Recommended fix High confidence

Chrome 148.0.7778.168 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. The browser will automatically check for and install updates
  3. Ensure the version displayed is 148.0.7778.168 or later
  4. Restart the browser if an update was installed
  5. Alternatively, download the latest Chrome from the official website (google.com/chrome) to ensure you have the most recent version
Caveat Chrome minor version upgrades typically have low risk of breaking changes; however, some older extensions or legacy web features may behave differently

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8529 — 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-8529 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