dbcve.org
ChromeWeb browser · Google

CVE-2026-11262

HIGH · 8.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
95/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
Use after free in TabStrip in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code 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 · high confidence

A use-after-free vulnerability exists in the TabStrip component of Google Chrome browsers prior to version 149.0.7827.53. This memory corruption flaw allows a remote attacker to execute arbitrary code through a specially crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to address 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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 installed Google Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' (Linux) or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties (Windows), or 'About Google Chrome' in the Chrome menu
    Affected if version number is lower than 149.0.7827.53
  2. Confirm Chrome is the active browser
    Identify which browser(s) are used in the environment - check installed browsers on Windows (Registry: HKLM\SOFTWARE\Clients\StartMenuInternet), Linux (dpkg -l | grep -i chrome or rpm -qa | grep -i chrome), or Mac (ls /Applications | grep -i chrome)
    Affected if Google Chrome is installed and used as a primary browser in the environment
  3. Verify TabStrip component presence
    The TabStrip is a core Chrome UI component that manages tab display in the browser's tab strip area. This component is built into Chrome and cannot be separately disabled - it is present in any standard Chrome installation
    Affected if Chrome is installed, the TabStrip component is inherently present and enabled as part of the standard Chrome UI
  4. Assess user exposure to web content
    Determine if users have the ability to browse arbitrary websites or open HTML files directly in Chrome. Check if organizational controls (proxy, sandboxing, URL filtering) restrict web browsing
    Affected if Users can navigate to untrusted or malicious web pages directly in Chrome, enabling the attack vector described in the CVE

You are affected if Google Chrome version is below 149.0.7827.53 and users can access web content directly in the browser, as the use-after-free in the TabStrip component triggers when processing malicious HTML pages.

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

Recommended fix High confidence

149.0.7827.53 or later

  1. Open Google Chrome browser
  2. Navigate to Settings > Help > About Google Chrome (or enter chrome://settings/help in the address bar)
  3. Chrome will automatically check for updates
  4. If update 149.0.7827.53 or later is available, click 'Update Google Chrome' to download and install it
  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
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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