CVE-2026-9878: 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 to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Critical)
HarborGuard Analysis
HarborGuard analysisSynopsis
A use-after-free vulnerability in ANGLE, the graphics abstraction layer bundled with Google Chrome, affects all Chrome versions prior to 148.0.7778.216. The flaw is reachable over the network without any authentication; a remote attacker only needs the victim to open a crafted HTML page. Successful exploitation enables arbitrary code execution inside the Chrome sandbox, giving the attacker control over the renderer process with access to confidential data, the ability to tamper with page content, and the potential to destabilize the browser. A patched-image rebuild at version 148.0.7778.216 is available on HarborGuard for environments running an affected version.
HarborGuard Coverage
Detection of CVE-2026-9878 is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against customer images in connected registries and CI pipelines, including custom-built images that bundle a Chromium or Chrome binary. Any image carrying a Chrome version below 148.0.7778.216 is flagged automatically.
AvailableHarborGuard scores this finding at CVSS 8.8 (High) and surfaces it accordingly in each customer org's triage queue, weighted further by any compliance policy the environment has configured for browser-engine vulnerabilities. Routing rules direct the finding to the appropriate team inbox based on image ownership and policy assignment within each customer org.
AvailableA patched-image rebuild pinned to Chrome 148.0.7778.216 becomes available on HarborGuard the moment the fix version is confirmed in the upstream advisory. For customers with auto-remediation enabled, HarborGuard triggers a rebuild, runs the configured regression suite against the new image, and opens a pull request against each affected workload; median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes in those environments.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker delivers the exploit over the network; the victim's browser must be able to reach or receive a crafted HTML page from an attacker-controlled origin.
- AuthenticationNot required
No account or credentials are needed; the attack works against any unauthenticated browser session that loads the malicious page.
- Victim interactionRequired
The victim must open or be redirected to a crafted HTML page, making this a social-engineering or malicious-link scenario.
- Attack complexityDetail
Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, specific memory layout, or other unpredictable environmental factors.
Blast Radius
- The attacker executes arbitrary code inside the Chrome renderer sandbox, gaining full control of the sandboxed process.
- Session tokens, saved credentials, and any page content loaded in the affected tab are readable by the attacker.
- The attacker can modify rendered page content, intercept form submissions, and inject malicious scripts into the browsing context.
- The renderer process can be crashed or destabilized, disrupting the user's browser session.
How HarborGuard Handles This
Available on HarborGuard: any image that packages Chrome below 148.0.7778.216 is flagged within minutes of the CVE entering upstream feeds. Where compliance policy permits auto-remediation, HarborGuard rebuilds the image at the patched version, runs the regression suite, and opens a pull request against affected workloads, targeting a median resolution time of around 90 minutes for high-severity findings. For environments where auto-remediation is not enabled, the finding appears in the triage queue with full CVSS context so teams can initiate a manual rebuild. Because this vulnerability requires victim interaction via a crafted HTML page, teams that cannot update immediately should consider network-policy controls that restrict which internal services can load arbitrary external URLs, and should evaluate whether any pipeline tooling embeds a Chrome binary used for headless rendering or screenshot capture, as those images carry the same risk.
Metrics
- CVSS v3.1
- 8.8
- Severity
- HIGH
- Fixed in
- 148.0.7778.216
- Affected Products
- 1
Fix available
- Google / Chrome< 148.0.7778.216 (from 148.0.7778.216)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H