dbcve.org
ChromeWeb browser · Google

CVE-2026-11115

HIGH · 7.3 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
73/100
Remediation priority · Elevated

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 Updater in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (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 · high confidence

A use-after-free vulnerability exists in the Google Chrome Updater component on Windows versions prior to 149.0.7827.53. A local attacker can exploit this by crafting a malicious file that triggers the use-after-free condition, allowing OS-level privilege escalation.

MitigationUpgrade Google Chrome on Windows to version 149.0.7827.53 or later to patch the vulnerability.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 Chrome is installed on Windows
    Check for Chrome installation in typical locations: C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Alternatively, query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\GoogleChromeBeta
    Affected if Chrome is not found on the Windows system, this CVE does not apply
  2. Retrieve installed Chrome version
    Right-click chrome.exe, select Properties, then view the Details tab for Product Version. Or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version' in Command Prompt
    Affected if Unable to determine the version, assume the system may be affected
  3. Compare version against affected range
    Parse the installed version number and compare it to 149.0.7827.53. The version format is Major.Minor.Build.Revision. Ensure all four components are evaluated numerically
    Affected if The installed version is less than 149.0.7827.53 (for example, 149.0.7827.52 or any earlier version)
  4. Confirm Windows platform
    Verify the operating system is Windows. Run 'systeminfo | findstr /B /C:"OS Name"' or check the SYSTEMROOT environment variable (typically C:\Windows)
    Affected if The system is not running Windows, this specific CVE does not apply as the vulnerability exists only in the Windows updater component

The system is affected if Google Chrome is installed on Windows with a version lower than 149.0.7827.53, since the use-after-free flaw in the Windows updater component requires both the vulnerable Chrome version and the Windows platform 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

Upgrade Google Chrome on Windows to version 149.0.7827.53 or later to patch the vulnerability.

Recommended fix High confidence

149.0.7827.53

  1. Open Google Chrome on the affected Windows machine
  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 display the current version
  6. If an update is available, click 'Update Google Chrome' to download and install it
  7. Restart the browser to complete the installation
  8. Verify the version by returning to About Google Chrome and confirming it shows version 149.0.7827.53 or later
Caveat Chrome updates are typically seamless; however, some extensions or settings may need to be reconfigured after major version updates

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-11115 — 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-11115 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