CVE-2026-9928: Out of bounds read in ANGLE in Google Chrome on Windows prior to 148
Out of bounds read in ANGLE in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)
HarborGuard Analysis
HarborGuard analysisSynopsis
An out-of-bounds read vulnerability in the ANGLE graphics layer of Google Chrome on Windows allows a remote attacker to execute arbitrary code. The attack is reachable over the network, requires no authentication, and is triggered when a user visits a crafted HTML page, meaning victim interaction is the only barrier. Successful exploitation gives the attacker full code execution in the context of the browser process, enabling data theft, system tampering, or further compromise. A patched-image rebuild at version 148.0.7778.216 is available on HarborGuard for affected environments.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against all customer images, including custom-built images that bundle or layer on top of Chrome on Windows. Any image carrying a Chrome version below 148.0.7778.216 is flagged automatically.
AvailableHarborGuard scores this finding at CVSS 8.8 (High) and is capable of weighting it further against each environment's compliance policy, such as stricter thresholds for internet-facing or regulated workloads. Triage alerts are routed to the appropriate team inbox within each customer organization based on configured ownership rules.
AvailableA patched-image rebuild pinned to Chrome 148.0.7778.216 becomes available through HarborGuard the moment the fix version is confirmed. For customers who opt into auto-remediation, HarborGuard triggers a rebuild, runs a regression test suite against the new 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 for environments with auto-remediation enabled.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker delivers the exploit over the network by serving a crafted HTML page, so the targeted host must be able to reach attacker-controlled web content.
- AuthenticationNot required
No account or credential is needed; any unauthenticated user who browses to the malicious page is a viable target.
- Victim interactionRequired
The user must open a crafted HTML page in the browser, making this a social-engineering or malvertising vector that requires at least one click or redirect.
- Attack complexityDetail
Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, memory layout randomization, or other environmental preconditions.
Blast Radius
- Attacker executes arbitrary code inside the Chrome browser process on the affected Windows host.
- Code execution at browser-process privilege allows reading of in-memory session tokens, saved credentials, and open tab content.
- The attacker can write or modify files accessible to the browser process, including cached data and user-profile storage.
- A compromised browser process can be used as a foothold to attempt privilege escalation or lateral movement within the host environment.
How HarborGuard Handles This
Available on HarborGuard: any image containing Google Chrome below version 148.0.7778.216 on Windows is detectable the moment this CVE enters the advisory feed, with matching running continuously against images in customer registries and CI pipelines. Where compliance policy permits auto-remediation, HarborGuard rebuilds the affected image at the patched version, executes a regression run, and opens a pull request against the relevant 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. For environments where auto-remediation is not enabled, the finding is surfaced in the triage queue with full CVSS detail so engineering teams can act manually. Until patching is complete, compensating controls such as network-policy rules that restrict browsing to untrusted origins and container-level egress filtering on affected workloads can reduce exposure.
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