dbcve.org
ChromeWeb browser · Google

CVE-2026-11281

MEDIUM · 5.0 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
50/100
Remediation priority · Moderate

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
Integer overflow in Chromoting in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted ETW event. (Chromium security severity: Low)

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

Integer overflow vulnerability in Chrome's Chromoting (remote desktop) component on Windows allows a local attacker to trigger the flaw via crafted ETW (Event Tracing for Windows) events, potentially exposing sensitive process memory contents. The vulnerability exists in versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. For enterprise environments, deploy via standard patch management or group policy to ensure consistent Chrome updates across Windows endpoints.

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/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. Identify Chrome installation on Windows
    Open Command Prompt or PowerShell and run: where chrome.exe or check C:\Program Files\Google\Chrome\Application\chrome.exe and C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    Affected if Chrome is installed on the Windows system
  2. Determine installed Chrome version
    Right-click chrome.exe, select Properties, then go to the Details tab to view File version, or run chrome.exe --version in command prompt
    Affected if The version number displayed is less than 149.0.7827.53
  3. Check if Chromoting feature is enabled
    Open Chrome, navigate to chrome://flags/#enable-remoting or check chrome://settings for remote desktop settings. Alternatively, check for me2me or remoting entries in Chrome policy files at HKLM\Software\Policies\Google\Chrome or HKCU\Software\Policies\Google\Chrome
    Affected if Chromoting/remoting feature is enabled or policies enabling it are present
  4. Verify Chrome process memory exposure risk
    This vulnerability allows reading sensitive data from process memory via crafted ETW events. Check if Chrome is running with high privileges or handling sensitive data, as this would increase the impact of exploitation
    Affected if Chrome runs with elevated privileges or handles sensitive information locally

A system is affected if Google Chrome for Windows is installed with a version prior to 149.0.7827.53 and the Chromoting/remoting feature is enabled, allowing a local attacker with system access to potentially read sensitive data from Chrome process memory.

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. For enterprise environments, deploy via standard patch management or group policy to ensure consistent Chrome updates across Windows endpoints.

Recommended fix High confidence

Chrome 149.0.7827.53 (stable channel)

  1. Open Chrome and go to Settings > Help > About Google Chrome
  2. Chrome will automatically check for and install the latest version
  3. Alternatively, download the latest Chrome stable build from chrome.google.com
  4. Restart Chrome after the update completes
  5. Verify the version by going to chrome://settings/help - it should show version 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
  • 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-11281 — 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-11281 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