dbcve.org
ChromeWeb browser · Google

CVE-2026-11026

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 Extensions in Google Chrome prior to 149.0.7827.53 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension. (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 · moderate confidence

This vulnerability in Chrome extensions prior to version 149.0.7827.53 allowed malicious extensions to bypass navigation restrictions due to an inappropriate implementation. An attacker would need to convince a user to install a crafted malicious extension, which could then circumvent Chrome's security controls around navigation behavior.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to receive the patch for this vulnerability. Organizations should also review and restrict extension installation policies to prevent users from installing untrusted extensions.

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. Check installed Chrome version
    Navigate to chrome://settings/help or use the Chrome menu > Help > About Google Chrome. The version number is displayed on that page.
    Affected if The displayed version is lower than 149.0.7827.53 (for example, 148.x.x.x or earlier).
  2. Review extension installation policy
    Open Group Policy Editor (gpedit.msc) on Windows or check chrome://policy for Enterprise policy settings. Look for 'ExtensionInstallForcelist', 'ExtensionInstallSources', or similar extension control policies.
    Affected if No restrictive extension policies are configured, allowing users to install extensions from any source.
  3. Inspect installed extensions
    Navigate to chrome://extensions and review the list of installed extensions. Check for any unknown, untrusted, or recently installed extensions that you did not intentionally add.
    Affected if Any extension is present that was not installed by your organization or that you do not recognize.
  4. Verify Chrome is up to date
    Visit chrome://settings/help and confirm there is no pending update. If an update is available, Chrome will show an update button.
    Affected if Chrome reports an available update or indicates the browser is not up to date.

You are affected if your Chrome version is below 149.0.7827.53 and your environment allows installation of extensions from untrusted or unknown sources.

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 receive the patch for this vulnerability. Organizations should also review and restrict extension installation policies to prevent users from installing untrusted extensions.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. 1. Open Google Chrome and navigate to chrome://settings/help
  2. 2. Chrome will automatically check for updates
  3. 3. If an update is available, click 'Update Google Chrome'
  4. 4. Restart Chrome to complete the update
  5. 5. Verify the version by going to chrome://settings/help and confirm the version is 149.0.7827.53 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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