ChromeWeb browser · Google
CVE-2026-11229
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 Enterprise in Google Chrome prior to 149.0.7827.53 allowed a local attacker to perform privilege escalation via physical access to the device. (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 confidenceGoogle Chrome prior to version 149.0.7827.53 contains an inappropriately implemented Enterprise feature that allows a local attacker with physical access to the device to escalate privileges. The vulnerability stems from a flaw in how the browser handles enterprise policies or configurations in certain scenarios.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionOpen Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://settings/help. The version number is displayed on that page.Affected if The version shown is lower than 149.0.7827.53 (e.g., 149.0.7827.50 or earlier).
-
Verify Enterprise enrollment statusOpen chrome://settings and look for the 'Managed by your organization' message at the bottom of the Settings page, or navigate to chrome://management to see enrollment details.Affected if Chrome shows as managed or enrolled to an enterprise domain (e.g., Google Admin, Microsoft Intune, or other MDM).
-
Check for active Chrome enterprise policiesNavigate to chrome://policy and review the 'Policy List' section. Look for any policies under the 'Enterprise' or 'Authentication' categories that are actively applied.Affected if Any Enterprise-related policies are listed as 'Enabled' or ' enforced, indicating the feature is in use.
A user is affected only if their Chrome version is below 149.0.7827.53 AND the Enterprise feature (managed browser policies or domain enrollment) is actively configured on the device.
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. Organizations should ensure standard endpoint management processes include timely browser updates, particularly for devices that may be left unattended.
Chrome 149.0.7827.53 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is lower than 149.0.7827.53, Chrome will automatically check for and download the update
- Wait for the update to download completely
- Click 'Relaunch' or restart Chrome to apply the update
- Verify the version now shows 149.0.7827.53 or higher in Settings > Help > About Google Chrome
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-11229 — 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-11229 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