ChromeWeb browser · Google
CVE-2026-11103
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 · uneditedInappropriate implementation in Installer 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 · moderate confidenceA local privilege escalation vulnerability exists in the Google Chrome installer for Windows. The 'inappropriate implementation' in the installer allows a local attacker with user-level access to elevate to OS-level (SYSTEM) privileges by placing a malicious file on the system. This is a local attack vector requiring the attacker to have some level of access to the target machine.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installed on WindowsCheck for Chrome installation by examining the registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or by looking for chrome.exe in common installation paths like C:\Program Files\Google\Chrome\Application\Affected if Google Chrome is present on the system
-
Determine installed Chrome versionRight-click chrome.exe and select Properties, then view the Details tab for the Version field. Alternatively, open Chrome and navigate to chrome://settings/help to display the current version number.Affected if The displayed version number is lower than 149.0.7827.53
-
Check Windows version contextSince the vulnerability requires a local attacker with file placement capability, verify if the system allows non-administrator users to write to directories accessible by the Chrome installer or temp folders.Affected if Standard users have write access to directories that the Chrome installer uses during installation or update processes
A system is affected if Google Chrome for Windows is installed with a version lower than 149.0.7827.53 and the environment permits local users to place files in installer-accessible locations.
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 for Windows to version 149.0.7827.53 or later. Organizations should deploy the update through their standard patch management processes.
Chrome 149.0.7827.53 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 149.0.7827.53, click 'Update Google Chrome' to upgrade to the latest version
- Restart Chrome after the update completes
- Alternatively, download Chrome from the official website (google.com/chrome) to get the latest stable version
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
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 locallyCheck whether your project pulls in CVE-2026-11103 — 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-11103 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