dbcve.org
ChromeWeb browser · Google

CVE-2026-11190

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 discretionary access control 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

A vulnerability in Google Chrome's extension system prior to version 149.0.7827.53 allowed malicious extensions to bypass discretionary access control mechanisms, potentially enabling unauthorized access to resources or data that should have been restricted by access controls.

MitigationUpdate Chrome to version 149.0.7827.53 or later. Review and audit installed browser extensions, removing any untrusted or unnecessary extensions, and implement organizational extension whitelisting policies.

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 menu Help > About Google Chrome to view the current version number
    Affected if The installed version is earlier than 149.0.7827.53
  2. Identify extensions loaded from outside the Chrome Web Store
    Go to chrome://extensions and look for extensions that have Developer mode enabled or are not sourced from the Chrome Web Store (they will show 'Remove' instead of just being from a verified developer)
    Affected if Any extension is installed that did not come from the Chrome Web Store, as the attack requires user installation of a malicious extension
  3. Review extension permissions
    In chrome://extensions, click 'Details' on each extension to review the permissions requested, looking for overly broad permissions that could be used to bypass access controls
    Affected if An installed extension requests permissions beyond what is necessary for its stated purpose, indicating potential misuse potential
  4. Check for Developer mode enabled
    Look at the top of chrome://extensions page for a 'Developer mode' toggle - if enabled, it allows loading unpacked extensions from any source
    Affected if Developer mode is turned on, which allows installation of extensions from any location without verification

You are affected if your Chrome version is earlier than 149.0.7827.53 AND you have installed any extension from an untrusted source or with elevated permissions.

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 Chrome to version 149.0.7827.53 or later. Review and audit installed browser extensions, removing any untrusted or unnecessary extensions, and implement organizational extension whitelisting policies.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. 1. Open Google Chrome on your device
  2. 2. Click the three-dot menu icon in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click 'About Google Chrome'
  5. 5. Chrome will automatically check for and download available updates
  6. 6. Wait for the update to complete (should show version 149.0.7827.53 or later)
  7. 7. Click 'Relaunch' or restart Chrome manually to apply the update
Caveat Chrome stable updates typically have minimal user-facing breaking changes;Extensions may need to be re-enabled if disabled during update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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