dbcve.org
ChromeWeb browser · Google

CVE-2026-10996

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Inappropriate implementation in Workers in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

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 a same-origin policy (SOP) bypass vulnerability in Google Chrome's Web Workers implementation. An inappropriate implementation allowed a remote attacker via a crafted HTML page to circumvent the SOP restrictions that normally prevent cross-origin access to sensitive resources.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. Organizations should ensure browser update policies are enforced or communicate the update requirement to end users.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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. Identify Chrome browser version
    Navigate to chrome://version in the Chrome address bar and note the version number displayed under 'Google Chrome' (e.g., 149.0.7827.53). Alternatively, click the three-dot menu > Help > About Google Chrome.
    Affected if The displayed version is lower than 149.0.7827.53 (e.g., 149.0.7827.50, 148.x.x.x, etc.)
  2. Confirm Workers feature usage
    Inspect the web application's source code or network traffic for usage of Web Workers (new Worker()), Service Workers (navigator.serviceWorker.register), or Shared Workers (new SharedWorker).
    Affected if The browser-based application uses any Workers API (web workers, service workers, or shared workers) to execute background tasks.
  3. Check for cross-origin worker scripts
    Review the application's worker script imports and registrations. Look for Worker, SharedWorker, or ServiceWorker constructors that reference cross-origin URLs (different origin from the parent page).
    Affected if The application loads worker scripts from cross-origin URLs, enabling the SOP bypass to access cross-origin resources through the worker context.

A user is affected if they run Google Chrome versions below 149.0.7827.53 AND browse web applications that use Workers (especially with cross-origin worker scripts), as the SOP bypass allows unauthorized cross-origin resource access.

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. Organizations should ensure browser update policies are enforced or communicate the update requirement to end users.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome browser
  2. Navigate to chrome://settings/help or go to Settings > Help > About Google Chrome
  3. Chrome will automatically check for updates and display the current version
  4. If an update is available, click 'Update Google Chrome' or wait for it to download automatically
  5. Restart the browser to apply the update
  6. After restart, verify the version by returning to chrome://settings/help to confirm version 149.0.7827.53 or later is installed
Caveat Browser update with minimal risk; ensure other browsing sessions are saved before restarting

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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