dbcve.org
ChromeWeb browser · Google

CVE-2026-10946

HIGH · 7.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
82/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
Heap buffer overflow in Media in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code inside a sandbox 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 · moderate confidence

Heap buffer overflow vulnerability in Google Chrome's Media component allows a remote attacker who tricks a user into performing specific UI gestures on a crafted HTML page to potentially execute arbitrary code within the sandbox environment.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch the vulnerability.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 via 'where chrome' in cmd. On Mac: 'ls /Applications | grep -i Chrome'. On Linux: which google-chrome or which chromium-browser
    Affected if Google Chrome is not present on the system, the user is not affected by this Chrome-specific vulnerability
  2. Determine installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux) or 'chrome --version' (Windows) in terminal/command prompt
    Affected if The installed version is lower than 149.0.7827.53 (e.g., 148.x, 147.x, etc.)
  3. Confirm Media component is accessible
    Verify Chrome can access media playback features by loading any media file or visiting a site with video/audio content. The vulnerability exists in the Media component handling.
    Affected if Media playback functions work normally (the component is enabled and active) - the vulnerability only applies when the Media component processes crafted content
  4. Verify attack surface exposure
    Confirm the browser has network access and can be directed to untrusted websites. Check if Chrome's sandbox is enabled by visiting chrome://sandbox
    Affected if The browser can access external websites and the sandbox is enabled (the vulnerability requires the sandbox context to be exploitable)

A user is affected if Google Chrome is installed with a version below 149.0.7827.53 and the Media component is functional and accessible through normal browser use.

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 vulnerability.

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 check for updates and automatically download version 149.0.7827.53 or later
  5. Restart Chrome to complete the update

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-10946 — 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-10946 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