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

CVE-2026-9885: Insufficient validation of untrusted input in UI in Google Chrome on Mac prior to 148

Insufficient validation of untrusted input in UI in Google Chrome on Mac 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: Critical)

HarborGuard Analysis

HarborGuard analysis

Synopsis

This is an insufficient input validation vulnerability in Google Chrome on macOS, affecting versions prior to 148.0.7778.216. The flaw is reachable over the network and requires no authentication, but does require a victim to visit a crafted HTML page, and it is only exploitable by an attacker who has already compromised the Chrome renderer process. Successful exploitation enables a full sandbox escape, giving the attacker the ability to read, modify, and disrupt data and processes outside the browser sandbox with high impact across confidentiality, integrity, and availability. A patched-image rebuild at version 148.0.7778.216 is available on HarborGuard for affected environments.

HarborGuard Coverage

Detection

Detection of CVE-2026-9885 is available across every HarborGuard environment. Vulnerability data is ingested from upstream feeds within minutes of publication and matched against customer images in registries and CI/CD pipelines, including custom-built images that bundle Chrome on macOS base layers.

Available
Triage

HarborGuard is capable of scoring this CVE at 8.3 HIGH (CVSS v3.1) and weighting that score against each environment's compliance policy to determine urgency. Triage routing routes findings to the appropriate team inbox within each customer organization based on configured ownership rules.

Available
Patch

A patched-image rebuild at Chrome 148.0.7778.216 is available on HarborGuard for any environment running an affected version. For customers who opt into auto-remediation, HarborGuard performs the rebuild, runs a regression test suite, 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 affected Chrome instance must be reachable by or directed to a remote origin.

  • AuthenticationNot required

    No credentials or authenticated session are needed; any unauthenticated remote attacker can serve the malicious page.

  • Victim interactionRequired

    The victim must navigate to or be socially engineered into opening the crafted HTML page in Chrome on macOS.

  • Attack complexityDetail

    Attack complexity is high because the attacker must have already compromised the Chrome renderer process before the sandbox escape primitive is reachable, introducing a significant precondition.

Blast Radius

  • Attacker escapes the Chrome browser sandbox on macOS, gaining code execution in a context outside the renderer's restricted environment.
  • With sandbox escape achieved, the attacker reads files and data accessible to the user running Chrome, including stored credentials, cookies, and session tokens.
  • The attacker modifies files, configuration, or persisted application data on the host system with the privileges of the Chrome process owner.
  • The attacker disrupts running processes or the operating system environment, up to and including crashing or destabilizing the affected host.

How HarborGuard Handles This

Available on HarborGuard: detection of CVE-2026-9885 is active for any customer image that bundles Google Chrome on a macOS base layer, with matching available within minutes of CVE publication. For environments where the installed Chrome version is below 148.0.7778.216, a rebuilt image pinned to the patched version is available. For customers who opt into auto-remediation, HarborGuard rebuilds the image, runs a regression test pass, and opens a pull request against affected workloads. For high-severity issues, the median time from CVE publication to a merged patch PR is around 90 minutes in environments with auto-remediation enabled. Where compliance policy restricts automated remediation, the finding is surfaced with full CVSS context and fix-version detail so engineering teams can act manually. Because this vulnerability requires a pre-compromised renderer process, teams may also consider network-policy controls that restrict which origins Chrome instances in containerized environments are permitted to contact, reducing the attacker's ability to deliver the crafted page in the first place.

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