dbcve.org
ChromeWeb browser · Google

CVE-2026-11246

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
60/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
Insufficient validation of untrusted input in IndexedDB in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)

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

A vulnerability in IndexedDB within Google Chrome allows a remote attacker who has already compromised the renderer process to bypass same origin policy restrictions due to insufficient validation of untrusted input. This enables potentially unauthorized access to IndexedDB data stores across origins through a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch the insufficient input validation in IndexedDB. Organizations should ensure browser update policies are enforced.

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

CVSS:3.1/AV:N/AC:H/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. Determine if Google Chrome is installed
    Check for Chrome installation by looking for chrome.exe on Windows (typically in Program Files\Google\Chrome\Application\) or Chrome.app on macOS (in /Applications/). Alternatively, try running 'google-chrome --version' on Linux or checking via system package manager.
    Affected if Google Chrome is installed on the system
  2. Obtain installed Google Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line, or check the application properties for the chrome.exe file.
    Affected if Unable to determine the version - cannot confirm patch status
  3. Compare installed version against vulnerable range
    Check if the installed version number is less than 149.0.7827.53. Version format is typically major.minor.build.patch (e.g., 149.0.7827.50). Any version from 149.0.0.0 up to 149.0.7827.52 is vulnerable.
    Affected if Installed version is less than 149.0.7827.53 (e.g., 148.x.x.x, 149.0.7827.50, etc.)
  4. Note: IndexedDB usage does not affect vulnerability status
    This is informational - the vulnerability exists in the Chrome IndexedDB implementation itself regardless of whether IndexedDB is actively used by any web application. The same-origin policy bypass applies when a compromised renderer process accesses IndexedDB data.
    Affected if Not applicable - this is not a condition that indicates vulnerability

A system is affected if Google Chrome is installed and the detected version is earlier than 149.0.7827.53.

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 insufficient input validation in IndexedDB. Organizations should ensure browser update policies are enforced.

Recommended fix High confidence

Chrome version 149.0.7827.53 or later (latest stable release)

  1. Open Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is less than 149.0.7827.53, Chrome will automatically check for and offer an update
  3. Click 'Update Google Chrome' if prompted, then restart the browser
  4. After restart, verify the version is 149.0.7827.53 or higher via Help > About Google Chrome

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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