dbcve.org
ChromeWeb browser · Google

CVE-2026-11644

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 149.0.7827.103 or later.
See remediation →
82/100
Remediation priority · High
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 Views in Google Chrome on Linux prior to 149.0.7827.103 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. (Chromium security severity: Critical)

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

Use-after-free vulnerability in Google Chrome's Views component on Linux allows a malicious Chrome extension to execute arbitrary code. The attacker must trick the user into installing a crafted malicious extension, which then triggers the UAF condition to achieve code execution.

MitigationUpdate Google Chrome for Linux to version 149.0.7827.103 or later. Organizations should review extension installation policies and consider restricting extension sources to trusted repositories.

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.103

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

CVSS:3.1/AV:N/AC:H/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. Verify the operating system is Linux
    Run 'uname -a' or check /etc/os-release to confirm the system is running Linux. This vulnerability only affects Chrome on Linux, not Windows or macOS.
    Affected if The system is running Linux (the vulnerability does not apply to Windows or macOS)
  2. Check installed Google Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' in terminal to display the installed version number.
    Affected if The installed version is lower than 149.0.7827.103
  3. Compare version against affected range
    If the version shown is, for example, 149.0.7827.0 or any build prior to 149.0.7827.103, the installation falls within the vulnerable range.
    Affected if The version number is less than 149.0.7827.103 (for example, 149.0.7827.0, 148.0.2821.99, etc.)
  4. Confirm Chrome Views component usage
    This vulnerability is in the Views UI framework. Most standard Chrome installations use Views on Linux. No specific config check is needed as this is internal to Chrome.
    Affected if Chrome is running on Linux with any version prior to 149.0.7827.103

The user is affected if running Google Chrome on Linux with a version number lower than 149.0.7827.103.

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.103 or later
Fixed in 149.0.7827.103
Interim mitigation

Update Google Chrome for Linux to version 149.0.7827.103 or later. Organizations should review extension installation policies and consider restricting extension sources to trusted repositories.

Recommended fix High confidence

149.0.7827.103

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 149.0.7827.103 or later
  6. Click 'Relaunch' or restart Chrome manually to apply the update
  7. Verify the version by returning to About Chrome and confirming the version number is 149.0.7827.103 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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