Insufficient validation of untrusted input in WebNN in Google Chrome on Windows prior to 149

Google lists CVE-2026-11063 as Medium in the Chrome 149 desktop release notes, describing it only as *insufficient validation of untrusted input in WebNN*; the affected range is Chrome on Windows prior to 149.0.7827.53/54. The user-supplied CVSS text implies a far worse outcome, but the public vendor note does not describe this like a default-reachable, whole-browser RCE. Based on the truncated wording you supplied and common Chrome advisory phrasing, this likely sits in a post-renderer / privileged-process path rather than a clean one-click browser takeover.

The vendor-severity story in public sources does not match the 9.6 baseline you supplied: Google itself shipped this bug in the Medium bucket, not the Critical bucket. That downgrade makes sense in practice because the chain appears to require more than 'visit page, get owned': it is Windows-only, tied to WebNN, and WebNN exposure in enterprise Stable populations is much narrower than ordinary Blink/V8 attack surface.

Why this verdict

• Major downward adjustment: likely post-compromise prerequisite — the supplied description fragment reads like Chrome's standard *'attacker who had compromised the renderer process'* wording, which means this is probably a chain component, not initial access.
• Exposure is materially narrower than the CVSS suggests — Windows-only is already a slice of the browser fleet, and WebNN is a much smaller surface than Blink/V8/Network.
• Threat intel is cold — no KEV, no public PoC, and an EPSS of 0.00043 do not support emergency treatment.

Why not higher?

A higher rating would require evidence that this is reliably reachable from an ordinary web page on default Chrome Stable populations, or evidence of live exploitation. We have neither. The public vendor treatment points the other way: Google bucketed it as Medium, which is not how Chrome flags a broadly weaponizable front-door browser RCE.

Why not lower?

I am not calling this IGNORE because browser-chain bugs can become valuable once paired with a renderer bug or a feature-exposure condition you did not know you had. It also sits in a privileged browser-adjacent area, so if you do have AI/browser experimentation rings on Windows, the consequence is still worth tracking and patching in normal cadence.

1. Force Chrome auto-update and relaunch compliance — Make sure Windows endpoints actually move to 149.0.7827.53/54 or later and users restart the browser so the patched binaries are loaded. For a LOW verdict there is no mitigation SLA; treat this as backlog hygiene and fold it into your normal browser-update enforcement cycle.
2. Shut off experimental browser exposure where possible — Review admin baselines, pilot rings, and developer workstations for chrome://flags usage or policies/processes that encourage experimental web-platform features. This matters most on Windows test populations; with a LOW verdict, do it during routine config hygiene rather than emergency change.
3. Use browser isolation for high-risk user groups — For users who routinely open untrusted links, browser isolation reduces the practical value of niche browser-chain bugs by moving risky rendering off the endpoint. This is a strategic control, not a same-day response, and belongs in your normal hardening program.

Run this on the target Windows endpoint as a normal user; admin rights are not required. Invoke it with powershell -ExecutionPolicy Bypass -File .\check-chrome-webnn-cve-2026-11063.ps1. The script checks installed Chrome versions and the current user's Chrome Local State for obvious WebNN / experimental flag exposure, then prints VULNERABLE, PATCHED, or UNKNOWN.

# check-chrome-webnn-cve-2026-11063.ps1

# Purpose: Assess likely exposure to CVE-2026-11063 on Windows Chrome.

# Output: VULNERABLE / PATCHED / UNKNOWN

# Exit codes: 0=PATCHED, 1=VULNERABLE, 2=UNKNOWN


$ErrorActionPreference = 'SilentlyContinue'

function Get-VersionObject {
    param([string]$Version)
    try { return [version]$Version } catch { return $null }
}

$fixed = Get-VersionObject '149.0.7827.53'
$chromePaths = @(
    "$env:ProgramFiles\Google\Chrome\Application\chrome.exe",
    "$env:ProgramFiles(x86)\Google\Chrome\Application\chrome.exe",
    "$env:LOCALAPPDATA\Google\Chrome\Application\chrome.exe"
) | Select-Object -Unique

$found = @()
foreach ($p in $chromePaths) {
    if (Test-Path $p) {
        $fv = (Get-Item $p).VersionInfo.FileVersion
        $vo = Get-VersionObject $fv
        if ($vo) {
            $found += [pscustomobject]@{ Path = $p; VersionString = $fv; Version = $vo }
        }
    }
}

if ($found.Count -eq 0) {
    Write-Output 'UNKNOWN'
    Write-Output 'Reason: Google Chrome executable not found in standard install paths.'
    exit 2
}

$allPatched = $true
$anyVulnerableVersion = $false
foreach ($item in $found) {
    if ($item.Version -lt $fixed) {
        $allPatched = $false
        $anyVulnerableVersion = $true
    }
}

if ($allPatched) {
    Write-Output 'PATCHED'
    $found | ForEach-Object { Write-Output ("Chrome: {0} [{1}]" -f $_.VersionString, $_.Path) }
    exit 0
}

# Check current user's Local State for obvious lab/experimental flags.

$localStatePath = Join-Path $env:LOCALAPPDATA 'Google\Chrome\User Data\Local State'
$flagEvidence = @()
if (Test-Path $localStatePath) {
    $raw = Get-Content -Raw -Path $localStatePath
    if ($raw -match 'WebMachineLearningNeuralNetwork') { $flagEvidence += 'WebMachineLearningNeuralNetwork' }
    if ($raw -match 'enable-experimental-web-platform-features') { $flagEvidence += 'enable-experimental-web-platform-features' }
    if ($raw -match 'webnn') { $flagEvidence += 'webnn' }
}

if ($anyVulnerableVersion -and $flagEvidence.Count -gt 0) {
    Write-Output 'VULNERABLE'
    $found | ForEach-Object { Write-Output ("Chrome: {0} [{1}]" -f $_.VersionString, $_.Path) }
    Write-Output ('Flag evidence: ' + ($flagEvidence | Select-Object -Unique -Join ', '))
    Write-Output 'Assessment: vulnerable version present and local profile shows experimental/WebNN-related exposure hints.'
    exit 1
}

Write-Output 'UNKNOWN'
$found | ForEach-Object { Write-Output ("Chrome: {0} [{1}]" -f $_.VersionString, $_.Path) }
Write-Output 'Assessment: vulnerable version present, but local checks did not prove WebNN reachability. Site-side origin trials and runtime conditions are not visible from this script.'
exit 2

Sources

1. Chrome Releases: Stable Channel Update for Desktop (June 2, 2026)
2. Chrome Releases: Early Stable Update for Desktop (May 29, 2026)
3. CISA Known Exploited Vulnerabilities Catalog
4. FIRST EPSS API documentation
5. Chrome for Developers: Get started with origin trials
6. Chromium issue 481776048 (search snippet indicates WebNN behind a flag)
7. Web Machine Learning implementation status