CVE-2026-10914: Use after free in ANGLE in Google Chrome on Windows prior to 149
Use after free in ANGLE in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Metrics
- CVSS v3.1
- 8.8
- Severity
- HIGH
- Fixed in
- 149.0.7827.53
- Affected Products
- 1
HarborGuard Analysis
Synopsis
A use-after-free vulnerability in ANGLE, the graphics abstraction layer used by Google Chrome on Windows, allows a remote attacker to execute arbitrary code inside the Chrome sandbox by luring a user to a crafted HTML page. The vulnerability is reachable over the network, requires no authentication, and does trigger when a victim visits a malicious page. Successful exploitation gives the attacker code execution within the Chrome sandbox process. A patched-image rebuild at version 149.0.7827.53 is available on HarborGuard for environments running an affected version of Chrome.
HarborGuard Coverage
Detection is available across every HarborGuard environment: CVE-2026-10914 is ingested from upstream feeds within minutes of publication and matched against customer images in connected registries and CI/CD pipelines, including custom-built images that bundle a Chrome or Chromium binary.
AvailableHarborGuard scores this CVE at 8.8 HIGH per CVSS v3.1 and weights it against each environment's compliance policy to determine urgency; findings are routed to the appropriate team inbox within each customer organization based on configured ownership rules.
AvailableA patched-image rebuild at Chrome 149.0.7827.53 is available on HarborGuard for any image found to include an affected Chrome version. For customers with auto-remediation enabled, HarborGuard triggers a rebuild, runs a regression test suite against the new image, and opens a pull request against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker delivers the exploit over the network by directing the victim to a remotely hosted crafted HTML page, so the affected Chrome instance must be reachable to a browser session with outbound internet or intranet access.
- AuthenticationNot required
No account or credentials are required; any unauthenticated visitor to the malicious page can be targeted.
- Victim interactionRequired
The victim must navigate to or be redirected to the attacker-controlled HTML page, making social engineering or a malicious advertisement a necessary part of the attack chain.
- Attack complexityDetail
Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, specific memory layout, or other environmental preconditions beyond the victim visiting the page.
Blast Radius
- The attacker gains arbitrary code execution inside the Chrome renderer sandbox process on the victim's Windows host.
- Confidentiality impact is high: the attacker can read process memory accessible to the renderer, including cached credentials, session tokens, and page content.
- Integrity impact is high: the attacker can write to and manipulate data within the sandbox, and a sandbox escape chained to this bug would extend write access further.
- Availability impact is high: the renderer process can be crashed or held, disrupting the browser session on the affected host.
How HarborGuard Handles This
Available on HarborGuard: any container image that bundles a Chrome or Chromium binary below version 149.0.7827.53 is flagged automatically within minutes of the CVE entering upstream feeds. For customers with auto-remediation enabled, HarborGuard initiates a patched rebuild at 149.0.7827.53, runs the configured regression tests against the rebuilt image, 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. Where compliance policy requires manual approval, the finding is queued at HIGH severity and routed to the designated owner inbox with full CVSS context and affected-image details. As an interim compensating control, customers can apply network policy to restrict outbound browsing from containers that embed Chrome, reducing the chance that a sandboxed process can reach attacker-controlled pages.
Fix available
- Google / Chrome< 149.0.7827.53 (from 149.0.7827.53)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H