dbcve.org
ChromeWeb browser · Google

CVE-2026-11170

HIGH · 8.1 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Chromoting in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to perform OS-level privilege escalation via malicious network traffic. (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 use-after-free vulnerability in Chrome's Chromoting (remote desktop) feature on Linux allowed a remote attacker to execute arbitrary code with elevated privileges by sending specially crafted network traffic, enabling OS-level privilege escalation.

MitigationUpdate Google Chrome for Linux to version 149.0.7827.53 or later to patch the Chromoting component.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 OS. This vulnerability only affects Chrome on Linux, not Windows or macOS.
    Affected if The system is running Linux and has Google Chrome installed
  2. Check if Google Chrome is installed
    Run 'google-chrome --version' or 'google-chrome-stable --version' in the terminal. Alternatively, check for /opt/google/chrome/google-chrome or look in common application directories.
    Affected if Google Chrome is installed on the Linux system
  3. Determine the installed Chrome version
    Execute 'google-chrome --version' to get the exact version number. Compare this against the affected range of versions prior to 149.0.7827.53.
    Affected if The installed version is lower than 149.0.7827.53
  4. Check if Chromoting feature is enabled
    Look for Chrome remote desktop configuration files in ~/.config/chrome-remote-desktop/ or check for the chrome-remote-desktop package/service. Also inspect Chrome's policies if managed centrally.
    Affected if The Chromoting (remote desktop) feature is enabled or installed on the system

A user is affected if they are running Google Chrome on Linux with a version lower than 149.0.7827.53 AND have the Chromoting feature enabled, as the vulnerability requires both conditions to be exploitable.

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 for Linux to version 149.0.7827.53 or later to patch the Chromoting component.

Recommended fix High confidence

149.0.7827.53 or later (Chrome Stable for Linux)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Check the current version number displayed
  3. If the version is earlier than 149.0.7827.53, Chrome will automatically check for and prompt you to install updates
  4. Click 'Update Google Chrome' if prompted, or wait for the automatic update to complete
  5. Restart Chrome to apply the update
  6. Alternatively, download the latest stable Chrome version from the official Google Chrome website (google.com/chrome) and reinstall

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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