Like finding a lock-pick that only works on a door nobody installed yet, and even then it only opens into a sealed room
CVE-2026-11102 is an inappropriate implementation flaw (CWE-474) in Chrome's Isolated Web Apps (IWA) subsystem affecting all versions prior to 149.0.7827.53. A remote attacker can craft a malicious file that, when opened by a victim, achieves arbitrary code execution — but explicitly inside Chrome's renderer sandbox. The sandbox boundary is intact; the attacker lands in a sealed process with no direct filesystem, network-pivot, or OS-level credential access. All desktop platforms (Windows, macOS, Linux, ChromeOS) running Chrome < 149.0.7827.53 are nominally in scope.
The NVD CVSS 8.8 HIGH rating is mechanically correct for network-reachable code execution with low complexity, but it is materially misleading in practice. Three factors conspire to make this far less dangerous than the score implies: (1) the sandbox containment caps real-world impact well below C:H/I:H/A:H — without a separate sandbox-escape bug the attacker cannot touch the host OS; (2) Isolated Web Apps are in early-access, limited to a small group of Google partners and not generally available to enterprise or consumer users, so the reachable attack surface is vanishingly small; (3) Chromium's own security team rated this Medium, reflecting their authoritative understanding of the sandbox model. noisgate agrees with Chromium's assessment and downgrades from HIGH 8.8 to MEDIUM 5.0.
4 steps from start to impact.
Attacker crafts malicious IWA bundle file
- Knowledge of IWA bundle format and the specific CWE-474 code path
- No public PoC or exploit code exists as of September 2026, raising the initial development cost
Victim opens or installs the malicious file
.swbn.- User interaction: victim clicks/opens the file
- Chrome < 149.0.7827.53 installed
- IWA feature must be enabled or available in the victim's Chrome build
- IWA is not generally available — limited to select Google partners; most Chrome installs cannot even process IWA bundles
- Enterprise email/web gateways block or quarantine unusual file types by default
- User must deliberately open an unfamiliar file format
IsolatedWebAppsAllowed set to false blocks the surface entirelyCode executes inside Chrome's renderer sandbox
- Steps 1-2 succeeded
- Chrome sandbox is not disabled (almost never disabled in enterprise)
- Sandbox confinement means the attacker has very limited ability to exfiltrate data or persist
- No known sandbox escape is chained with this CVE
- Blast radius is limited to data visible to the renderer process (current page context)
Attacker attempts post-exploitation from sandbox
- A second, independent sandbox escape vulnerability in the same Chrome version
- Or a kernel vulnerability reachable from the sandboxed process
- Chrome sandbox escapes are extremely rare and high-value (typically worth $100K+ on bug bounty markets)
- No chained exploit has been reported or demonstrated for this CVE
- Google's VRP and Project Zero actively hunt sandbox escapes, making dwell time minimal
IsolatedWebAppsAllowed policy to false (or leave at default, which disables IWA for non-partner installs) via Group Policy, Intune, or Chrome Browser Cloud Management. This eliminates the attack surface entirely by preventing Chrome from processing IWA bundles. No noisgate mitigation SLA applies for MEDIUM — go straight to the 365-day remediation window, but this zero-effort policy change should be deployed immediately as hygiene..swbn (Signed Web Bundle) and related IWA file extensions are blocked or quarantined at email gateways (Proofpoint, Mimecast, Microsoft Defender for Office 365) and web proxy/CASB layers. This breaks Step 2 of the attack path by preventing delivery of the malicious file. Apply within your standard change window.- WAF / network IDS — This is a client-side browser vulnerability triggered by a local file, not a network-exploitable server flaw. Network-layer defenses cannot inspect or block the exploitation once the file reaches the endpoint.
- Chrome Site Isolation — Site Isolation is a separate security mechanism that isolates different web origins into different processes. It does not affect IWA bundle processing, which is a distinct code path.
- Disabling JavaScript — The vulnerability is in Chrome's IWA loader/implementation, not in script execution. Disabling JavaScript would break most web functionality and would not necessarily prevent the inappropriate implementation from being triggered during bundle parsing.
The supporting signals.
| In-the-Wild Exploitation | None reported. Not listed in CISA KEV. No known campaigns or threat-actor usage. No advisories from Google TAG or Mandiant reference this CVE. |
|---|---|
| Proof-of-Concept Availability | None found. Checked pocindex.io, GitHub (site:github.com CVE-2026-11102), ExploitDB, and SecureWithUmer/CVE-2026-PoCs — no dedicated repos, nuclei templates, or PoC code exist as of September 2026. The Chromium issue tracker entry (issues.chromium.org/500468338) is likely restricted. |
| EPSS Score | 0.00371 (0.37%), 30th percentile. Well below the threshold for concern — indicates the statistical model sees very low exploitation likelihood. |
| CISA KEV Status | Not listed. No federal binding operational directive applies. |
| CVSS Vector Interpretation | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H — The vector claims high impact across CIA triad, but Scope: Unchanged means the impact is confined to the vulnerable component (the sandboxed renderer). The C:H/I:H/A:H ratings are overstated because the sandbox limits what 'high confidentiality impact' actually means in practice. |
| Chromium Severity | Medium — Google's own security team rated this Medium, two full tiers below the NVD CVSS 8.8 HIGH. Chromium's severity takes sandbox containment into account; the NVD scoring does not. |
| Affected Versions | All Google Chrome versions prior to 149.0.7827.53 (Stable channel, released June 4, 2026) on Windows, macOS, Linux, and ChromeOS. |
| IWA Feature Availability | Isolated Web Apps are not generally available. Per Google's FAQ, IWA access is limited to a select group of partners. Enterprise Windows support was added in Chrome 161 (post-fix). The vast majority of Chrome installations cannot interact with IWA bundles. |
| Scanning & Exposure | Client-side browser vulnerability — not detectable via Shodan/Censys/GreyNoise. Enterprise detection relies on Chrome version auditing via endpoint management (SCCM, Intune, osquery, Chrome Browser Cloud Management). |
| Disclosure & Credit | Disclosed June 4, 2026 in the Chrome 149 stable channel update. The Chrome 149 release patched a record 429 vulnerabilities. Reporting researcher not publicly credited in available sources. |
Sources.
Why this verdict
- Sandbox containment caps real impact. The description explicitly states code execution occurs *inside a sandbox*. Chrome's renderer sandbox (seccomp-bpf on Linux, restricted tokens + AppContainer on Windows, Seatbelt on macOS) prevents filesystem access, credential theft, and lateral movement. Without a chained sandbox escape — a separate, rare, high-value bug — the attacker is stuck. This single factor invalidates the C:H/I:H/A:H CVSS impact ratings for practical purposes.
- Chromium's own team rates it Medium. Google's security team, who architected the sandbox and understand its bounds intimately, assigned Medium severity. When the vendor *downgrades their own bug*, that is a strong signal. The NVD 8.8 is a mechanical CVSS calculation that ignores sandbox context.
- IWA attack surface is nearly zero. Isolated Web Apps are in early access, restricted to a small group of Google partners. They are not enabled by default, not available to general enterprise or consumer Chrome installs, and enterprise Windows support didn't arrive until Chrome 161. The fraction of Chrome installations that can even trigger this bug is negligible — well under 1%.
- User interaction required with an exotic file type. The victim must open a malicious
.swbnor IWA-related file — a format essentially unknown to end users. Enterprise email gateways and web filters will block or quarantine these by default. This is not a drive-by-browsing scenario. - Role multiplier: Chrome is deployed on virtually every enterprise endpoint, but the affected component (IWA subsystem) is active on nearly none of them. Even on high-value hosts where Chrome is present (DCs, jump boxes, admin workstations), the IWA subsystem is inactive, and the sandbox confines the blast radius to the browser process. The realistic blast radius is *renderer process* — not host, not domain, not fleet. No high-value-role floor override applies because the chain dead-ends inside the sandbox without a second independent vuln.
- No exploitation pressure. EPSS 0.37%, no KEV listing, no public PoC, no known campaigns. There is zero urgency signal from the threat landscape.
Why not higher?
The CVSS 8.8 HIGH rating would be appropriate if code execution broke out of the sandbox and reached the host OS — but it explicitly does not. The description says *inside a sandbox*, and no chained escape exists. The IWA feature's near-zero deployment footprint means the reachable population is negligible. Chromium's own Medium rating confirms the sandbox containment is working as designed and meaningfully limits impact.
Why not lower?
Chrome is the world's most-deployed browser, so even a niche feature vulnerability in Chrome has a non-zero tail risk. If IWAs achieve broader adoption (which is Google's stated intent), this attack surface grows. The sandboxed code execution could theoretically be chained with a future sandbox escape, and the code execution primitive itself — even confined — has value to a sophisticated attacker building a multi-stage chain. These factors justify MEDIUM over LOW.
Crowdsourced verification payload.
Run on each target Windows endpoint (or push via SCCM/Intune script deployment). Requires no elevation — reads Chrome's version from the registry. Example: .\Check-CVE-2026-11102.ps1
#Requires -Version 5.1
<#
.SYNOPSIS
Check whether the installed Google Chrome version is vulnerable to CVE-2026-11102.
.DESCRIPTION
Reads Chrome version from the registry (HKLM and HKCU) and compares against
the fixed version 149.0.7827.53. Also checks if Isolated Web Apps are
enabled via enterprise policy.
.OUTPUTS
VULNERABLE / PATCHED / UNKNOWN
#>
$FixedVersion = [version]'149.0.7827.53'
$ChromePaths = @(
'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe',
'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe'
)
$VersionKeys = @(
'HKLM:\SOFTWARE\Google\Chrome\BLBeacon',
'HKLM:\SOFTWARE\WOW6432Node\Google\Chrome\BLBeacon',
'HKCU:\SOFTWARE\Google\Chrome\BLBeacon'
)
$IWAPolicyKey = 'HKLM:\SOFTWARE\Policies\Google\Chrome'
$ChromeInstalled = $false
$InstalledVersion = $null
foreach ($key in $VersionKeys) {
if (Test-Path $key) {
$ver = (Get-ItemProperty -Path $key -Name 'version' -ErrorAction SilentlyContinue).version
if ($ver) {
$ChromeInstalled = $true
try { $InstalledVersion = [version]$ver } catch { }
break
}
}
}
if (-not $ChromeInstalled) {
# Fallback: try chrome.exe --version
$chromePath = (Get-Command chrome.exe -ErrorAction SilentlyContinue).Source
if ($chromePath) {
$ChromeInstalled = $true
$verStr = (& $chromePath --version 2>$null) -replace '[^0-9.]',''
try { $InstalledVersion = [version]$verStr } catch { }
}
}
if (-not $ChromeInstalled) {
Write-Output 'UNKNOWN - Google Chrome not detected on this system.'
exit 2
}
if (-not $InstalledVersion) {
Write-Output 'UNKNOWN - Chrome installed but version could not be determined.'
exit 2
}
# Check IWA policy
$IWAEnabled = $null
if (Test-Path $IWAPolicyKey) {
$iwaPolicy = (Get-ItemProperty -Path $IWAPolicyKey -Name 'IsolatedWebAppsAllowed' -ErrorAction SilentlyContinue).IsolatedWebAppsAllowed
if ($null -ne $iwaPolicy) { $IWAEnabled = [bool]$iwaPolicy }
}
$iwaNote = if ($IWAEnabled -eq $true) { ' [IWA ENABLED via policy]' }
elseif ($IWAEnabled -eq $false) { ' [IWA DISABLED via policy - not exploitable]' }
else { ' [IWA policy not set - default: disabled for non-partners]' }
if ($InstalledVersion -lt $FixedVersion) {
Write-Output "VULNERABLE - Chrome $InstalledVersion < $FixedVersion$iwaNote"
exit 1
} else {
Write-Output "PATCHED - Chrome $InstalledVersion >= $FixedVersion$iwaNote"
exit 0
}