dbcve.org
ChromeWeb browser · Google

CVE-2026-10960

HIGH · 8.3 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
90/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
Uninitialized Use in Codecs in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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

This is an uninitialized memory use vulnerability in the codecs component of Google Chrome. A remote attacker who has already compromised the renderer process (Chrome's sandboxed process for web content) can exploit this flaw to potentially escape the sandbox isolation via a crafted HTML page. The vulnerability affects Chrome versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch the uninitialized use vulnerability in the codecs. Organizations should prioritize patching due to the high CVSS score and sandbox escape potential.

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

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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 installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or use 'Help > About Google Chrome' menu. The version number is displayed on the page that opens.
    Affected if The displayed version is lower than 149.0.7827.53 (for example, 149.0.7827.0 or earlier).
  2. Verify Chrome version via command line
    On Windows, open Command Prompt and run: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. On Linux, run: google-chrome --version or chromium --version.
    Affected if The returned version number is less than 149.0.7827.53.
  3. Confirm media codec functionality is in use
    The vulnerability exists in media codec processing. Visit chrome://media-internals to see active media sessions and codec information. This confirms the feature is enabled and processing media.
    Affected if Media sessions appear in the media-internals page, indicating active media playback using the vulnerable codec pathway.

A user is affected if their Google Chrome version is lower than 149.0.7827.53 and they use the browser to play media content that triggers the media codec code path.

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

Update Google Chrome to version 149.0.7827.53 or later to patch the uninitialized use vulnerability in the codecs. Organizations should prioritize patching due to the high CVSS score and sandbox escape potential.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome
  2. Click the three-dot menu in the top-right corner
  3. Navigate to Help > About Google Chrome
  4. Chrome will automatically check for updates
  5. If an update is available, click 'Update Google Chrome'
  6. Restart the browser to apply the update
  7. Verify the version by going to Help > About Google Chrome and confirm the version is 149.0.7827.53 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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