ChromeWeb browser · Google
CVE-2026-11146
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 · uneditedInsufficient validation of untrusted input in Chromoting in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (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 confidenceInsufficient input validation in Chrome's Chromoting (remote desktop) feature allowed a remote attacker with a compromised renderer process to potentially escape the sandbox via a crafted HTML page. This is a privilege escalation from compromised renderer to broader system access.
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
< 149.0.7827.53CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version numberAffected if The installed version is lower than 149.0.7827.53
-
Confirm Chromoting is in useVerify if the Chrome Remote Desktop feature is installed or enabled on the system. This may appear as a Chrome extension, a native host installer, or the chrome-remote-desktop serviceAffected if Chromoting/Chrome Remote Desktop is installed and active on the system
-
Determine if untrusted HTML content can be loadedAssess whether the Chrome instance can load arbitrary or untrusted HTML content (e.g., browsing the web, opening local HTML files, or visiting user-supplied content)Affected if The Chrome instance can load untrusted HTML pages without additional sandboxing layers
The system is affected if Chrome version is below 149.0.7827.53 AND Chromoting is installed AND the browser can load untrusted HTML content, allowing a compromised renderer to potentially escape the sandbox.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.53
Update Google Chrome to version 149.0.7827.53 or later. For enterprise environments, deploy the update via standard patch management processes.
149.0.7827.53 or later
- Open Google Chrome and click the three-dot menu (Settings) in the top right corner
- Navigate to 'About Chrome' in the left sidebar
- Chrome will automatically check for updates; if update is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
- Verify the version by visiting chrome://help - it should show 149.0.7827.53 or later
- For enterprise environments, use group policy or enterprise deployment tools to push version 149.0.7827.53 or later to all managed devices
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
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-11146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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