dbcve.org
ChromeWeb browser · Google

CVE-2026-10983

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
100/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
Insufficient validation of untrusted input in Dawn in Google Chrome prior to 149.0.7827.53 allowed a remote attacker 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

A sandbox escape vulnerability exists in Google's Dawn WebGPU implementation within Chrome. Insufficient validation of untrusted input allows a remote attacker to potentially escape the browser sandbox and execute code on the underlying system via a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch this sandbox escape vulnerability. Organizations should prioritize browser patch management and ensure endpoints receive security updates promptly.

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

CVSS:3.1/AV:N/AC:L/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. Verify Google Chrome is installed
    Check for Chrome installation by looking for chrome.exe in typical locations (e.g., C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\) or by running 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome -ErrorAction SilentlyContinue | Select-Object DisplayVersion' on Windows, or 'google-chrome --version' on Linux/Mac
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    On Windows: Open Chrome, go to Settings > About Chrome, or run 'google-chrome --version' from command line. On Mac: 'Google Chrome --version'. On Linux: 'google-chrome --version' or check /opt/google/chrome/resources/manifest.json
    Affected if Installed version is less than 149.0.7827.53 (e.g., 148.x.x.x, 147.x.x.x, etc.)
  3. Confirm WebGPU/Dawn is enabled
    In Chrome, navigate to chrome://flags/#enable-webgpu-developer-features or chrome://gpu/ and check for WebGPU-related flags. WebGPU is enabled by default in modern Chrome but verify the feature is not explicitly disabled
    Affected if WebGPU is enabled (default state); the vulnerability only applies when WebGPU is accessible to the browser

User is affected if Google Chrome is installed with a version prior to 149.0.7827.53 AND WebGPU/Dawn functionality is enabled in the browser

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 this sandbox escape vulnerability. Organizations should prioritize browser patch management and ensure endpoints receive security updates promptly.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome and navigate to Help > About Google Chrome
  2. Click 'Update Google Chrome' if an update is available, or wait for automatic update to download
  3. Restart the browser after the update completes to apply the security fix
  4. Alternatively, download the latest Chrome version directly from the official Google Chrome website (google.com/chrome)
Caveat Chrome updates are generally backward compatible for end users; some web apps or extensions may require adjustments due to security policy changes

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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