ChromeWeb browser · Google
CVE-2026-11120
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 Enterprise Reporting 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 · high confidenceInsufficient validation of untrusted input in Chrome's Enterprise Reporting component allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a crafted HTML page. This is a medium-severity Chromium vulnerability that enables privilege escalation from a already-compromised renderer.
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 Google Chrome installationOpen Chrome, navigate to chrome://version, or run 'google-chrome --version' (Linux) or check Programs and Features (Windows)Affected if Chrome is not installed or is installed at all (this is the prerequisite)
-
Determine installed Chrome versionLook at the version number shown in chrome://version or the --version output. Note the full version string (e.g., 149.0.7827.51)Affected if The version number is less than 149.0.7827.53 (e.g., 149.0.7827.51, 148.0.2345.67, etc.)
-
Check if Enterprise Reporting is enabledOn Windows, check Registry key HKLM\SOFTWARE\Policies\Google\Chrome\EnterpriseReportingEnabled or look for enterprise reporting policies configured via Group Policy. On Linux, check /etc/opt/chrome/policies/managed/ for JSON policy files containing EnterpriseReportingEnabledAffected if Enterprise Reporting is enabled in the environment (creates the attack surface for this vulnerability)
A user is affected if they have Google Chrome installed with a version lower than 149.0.7827.53 AND the Enterprise Reporting feature is enabled, making the sandbox escape path accessible.
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 to patch the insufficient input validation in Enterprise Reporting.
149.0.7827.53 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' > 'About Google Chrome'
- The browser will check for updates automatically
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
- Verify the version by returning to Help > About Google Chrome and confirming the version is 149.0.7827.53 or higher
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
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 locallyCheck whether your project pulls in CVE-2026-11120 — 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-11120 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