ChromeWeb browser · Google
CVE-2026-11102
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 Isolated Web Apps in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceA vulnerability in Google Chrome's Isolated Web Apps feature allows a remote attacker to execute arbitrary code inside a sandbox by tricking a user into opening a malicious file. The flaw stems from an inappropriate implementation in the Isolated Web Apps functionality prior to version 149.0.7827.53.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Check installed Chrome versionNavigate to chrome://version in the Chrome address bar and note the version number displayed, or run 'google-chrome --version' on Linux, or check the application info on macOS/Windows.Affected if The displayed version is less than 149.0.7827.53 (e.g., 149.0.7827.0, 148.x.x.x, etc.)
-
Verify Isolated Web Apps feature is enabledNavigate to chrome://flags/#enable-isolated-web-apps in the Chrome address bar and check if the feature is set to 'Enabled'. Alternatively, check if Group Policy enforces this feature on enterprise-managed devices.Affected if The Isolated Web Apps flag shows 'Enabled' or enterprise policy enables this feature.
-
Confirm sandbox configuration is defaultThis vulnerability's impact is reduced because the malicious code runs in Chrome's sandbox. Verify the sandbox is not disabled by navigating to chrome://sandbox or checking for '--no-sandbox' command-line arguments.Affected if The sandbox is enabled (default state). Note: while the sandbox limits risk, exploitation is still possible.
You are affected if your Chrome version is below 149.0.7827.53 AND the Isolated Web Apps feature is currently enabled in your browser or via enterprise policy.
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. No additional network-level mitigations are available; client-side patching is required.
Chrome 149.0.7827.53 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check your current version
- If the version is below 149.0.7827.53, Chrome will automatically check for and install updates
- Restart Chrome after the update completes to ensure the fix is applied
- Verify the version now shows 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
- 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-11102 — 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-11102 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