HarborGuard / CVE
Back to search
HIGHCVE-2026-9937Published Modified CNA Chrome

CVE-2026-9937: Use after free in UI in Google Chrome on Windows prior to 148

Use after free in UI in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

HarborGuard Analysis

HarborGuard analysis

Synopsis

Use-after-free in the UI layer of Google Chrome on Windows (versions prior to 148.0.7778.216) allows a remote attacker who has already compromised the renderer process to escape the browser sandbox via a crafted HTML page. The attack is reachable over the network but requires the victim to visit or interact with attacker-controlled content, and exploitation is conditional on the renderer already being compromised, meaning this is typically chained with a separate renderer exploit. Successful exploitation gives the attacker code execution outside the Chrome sandbox, effectively running arbitrary code at the privilege level of the browser process on the victim's Windows host. A patched-image rebuild at version 148.0.7778.216 is available on HarborGuard for environments running an affected version.

HarborGuard Coverage

Detection

Detection of CVE-2026-9937 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of ingestion from upstream advisory feeds, including custom-built images that bundle a Chromium or Chrome runtime. Any image in a connected registry or CI pipeline running Chrome below 148.0.7778.216 on Windows is flagged automatically.

Available
Triage

HarborGuard scores this CVE at 8.3 HIGH using the published CVSS v3.1 vector and can weight that score further against each customer environment's compliance policy, for example elevating priority for workloads exposed to untrusted web content. Triage findings are routed to the appropriate team inbox within each customer org based on image ownership and policy configuration.

Available
Patch

A patched-image rebuild pinned to Chrome 148.0.7778.216 becomes available in HarborGuard the moment the fix version is resolvable from upstream. For customers with auto-remediation enabled, HarborGuard triggers a rebuild, runs a regression test suite against the updated image, and opens a pull request against affected workloads automatically.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker delivers the crafted HTML page over the network, so the victim's browser must be reachable or directed to an attacker-controlled origin.

  • AuthenticationNot required

    No account or credentials are needed; any unauthenticated user browsing to the crafted page can be targeted.

  • Victim interactionRequired

    The victim must visit or otherwise interact with a crafted HTML page, introducing a social-engineering step for the attacker.

  • Attack complexityDetail

    Exploitation is rated AC:H because it depends on the renderer process already being compromised, typically through a separate chained vulnerability, before this use-after-free can be triggered for the sandbox escape.

Blast Radius

  • Attacker executes arbitrary code outside the Chrome sandbox at the privilege level of the browser process on the victim's Windows host.
  • Confidential data accessible to the browser process, including stored credentials, session cookies, and local files readable by that user, is exposed to the attacker.
  • The attacker can write to or modify files and registry entries accessible to the browser process user account.
  • The browser process and dependent services can be crashed or made unavailable on the affected host.

How HarborGuard Handles This

Available on HarborGuard: images containing Google Chrome below 148.0.7778.216 are flagged at ingestion, scored at 8.3 HIGH, and a rebuilt image at the fixed version is made available automatically. For customers with auto-remediation enabled, HarborGuard rebuilds the image, runs a regression test pass, and opens a pull request against affected workloads; median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes in environments with auto-remediation enabled. Because this vulnerability requires a pre-compromised renderer process as a prerequisite, teams that cannot update immediately should consider network-policy controls that restrict which origins workloads can load, reducing the attack surface for renderer exploitation that would precede this sandbox escape.

See how HarborGuard automates this

Metrics

CVSS v3.1
8.3
Severity
HIGH
Fixed in
148.0.7778.216
Affected Products
1

Fix available

148.0.7778.216
Affected packages
  • Google / Chrome
    < 148.0.7778.216 (from 148.0.7778.216)
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H