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

CVE-2026-9946: Use after free in ANGLE in Google Chrome prior to 148

Use after free in ANGLE in Google Chrome 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 ANGLE (the graphics abstraction layer inside Google Chrome) affects all Chrome versions before 148.0.7778.216. The vulnerability is reachable over the network and requires no credentials, but it does require the attacker to have already compromised the renderer process and to trick a user into visiting a crafted HTML page. Successful exploitation enables a full sandbox escape, giving the attacker high-confidence access to confidential data, the ability to tamper with system state, and the ability to crash or destabilize the browser. A patched-image rebuild at 148.0.7778.216 is available on HarborGuard for environments running an affected version.

HarborGuard Coverage

Detection

Detection for CVE-2026-9946 is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against images in customer registries, CI/CD pipelines, and custom-built images that bundle Chrome or Chromium. Any image carrying a Chrome version below 148.0.7778.216 is flagged automatically.

Available
Triage

HarborGuard scores this CVE at 8.3 HIGH (CVSS v3.1) and is capable of weighting that score against each customer environment's compliance policy to produce a priority ranking. Triage findings are routed to the team inbox or ticketing integration configured inside each customer org.

Available
Patch

A patched-image rebuild at Chrome 148.0.7778.216 becomes available through HarborGuard the moment the upstream release is confirmed in the advisory feed. For customers who opt into auto-remediation, HarborGuard rebuilds the affected image, runs a regression test suite, 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.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker must reach the victim's browser over the network by delivering a crafted HTML page, making this an over-the-network exposure.

  • AuthenticationNot required

    No credentials or account access are needed; the attack is available to any remote party who can serve content to the target.

  • Victim interactionRequired

    The victim must visit or be redirected to a crafted HTML page, requiring a social-engineering or malicious-link step.

  • Attack complexityDetail

    Attack complexity is rated High, meaning the attacker must also have an already-compromised renderer process in place before the sandbox-escape primitive is reachable.

Blast Radius

  • A successful attacker escapes the Chrome sandbox and gains execution context outside the browser's process isolation boundary.
  • Confidential data accessible to the browser process, including stored credentials, session tokens, and browsing history, becomes readable.
  • The attacker can modify files, registry entries, or other persisted state on the host that the browser user account has write access to.
  • The attacker can crash or hang Chrome and any dependent services, causing service disruption for the affected user session.

How HarborGuard Handles This

Available on HarborGuard: images containing Chrome below 148.0.7778.216 are detected automatically on ingest, scored at 8.3 HIGH, and surfaced through each customer's configured triage routing. A rebuilt image at the fixed version (148.0.7778.216) is available for environments where the image build context includes Chrome or Chromium. For customers who opt into auto-remediation, HarborGuard rebuilds the image, runs regression tests, and opens a pull request against affected workloads; median time from CVE publication to a merged patch PR for high-severity issues is around 90 minutes for environments with auto-remediation enabled. Where compliance policy does not permit automated remediation, the finding is queued as a manual action item with full CVSS detail and affected image digest attached.

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