CVE-2026-9966: Integer overflow in XML in Google Chrome on Windows prior to 148
Integer overflow in XML in Google Chrome on Windows 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 analysisSynopsis
An integer overflow in the XML parsing component of Google Chrome on Windows (versions prior to 148.0.7778.216) allows a remote attacker who has already compromised the renderer process to escape Chrome's sandbox via a crafted HTML page. The attack requires network access, no prior authentication, but does require the victim to visit a malicious page; it also requires the attacker to first have compromised the renderer, raising the practical bar. Successful exploitation gives the attacker code execution outside the sandbox, effectively breaking Chrome's primary isolation boundary. A patched-image rebuild at 148.0.7778.216 is available on HarborGuard for environments running an affected version.
HarborGuard Coverage
Detection of CVE-2026-9966 is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against all customer images in connected registries and CI/CD pipelines, including custom-built images that bundle Chrome or Chromium. Any image carrying a Chrome version below 148.0.7778.216 on a Windows base is flagged automatically.
AvailableHarborGuard scores this CVE at 8.3 HIGH using the published CVSS v3.1 vector and weights the finding against each customer environment's compliance policy to determine urgency and routing. Triage findings are delivered to the team or inbox configured in each customer org, ensuring the right engineers see the alert without manual sorting.
AvailableA patched-image rebuild at Chrome 148.0.7778.216 becomes available through HarborGuard the moment the fix version is resolvable from the upstream feed. 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 in environments with auto-remediation enabled.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker delivers the exploit over the network by directing the victim to a crafted HTML page, so the service (the victim's browser session) must be reachable or the victim must navigate to an attacker-controlled URL.
- AuthenticationNot required
No account or credential is needed; the attacker operates as an anonymous remote party.
- Victim interactionRequired
The victim must open or be redirected to a crafted HTML page, making a social-engineering or drive-by delivery step necessary.
- Attack complexityDetail
Attack complexity is rated High because the attacker must first compromise the Chrome renderer process before the integer overflow can be used for a sandbox escape, introducing a prerequisite exploitation step that is not guaranteed to succeed reliably.
Blast Radius
- Breaks Chrome's sandbox on Windows, giving the attacker code execution in the context of the browser process outside the renderer jail.
- Reads files, credentials, and session data accessible to the Windows user account running Chrome.
- Writes or modifies files on the host filesystem under that user's permissions, enabling persistence or payload staging.
- Crashes or destabilizes the browser process, causing a denial of service for the affected session.
How HarborGuard Handles This
Available on HarborGuard: any image containing Google Chrome below 148.0.7778.216 on a Windows base is matched against this CVE within minutes of the advisory entering the upstream feed. Where compliance policy permits, a rebuilt image at 148.0.7778.216 is made available immediately; for customers who opt into auto-remediation, HarborGuard runs the full rebuild-regression-PR flow with a median time to merged patch PR of around 90 minutes for high-severity findings. Given the sandbox-escape nature of this vulnerability, teams that cannot immediately update are advised to enforce network policies that restrict which origins users can reach from containerized browser workloads, and to gate any HTML rendering features behind feature flags until the patched image is deployed.
Metrics
- CVSS v3.1
- 8.3
- 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:H/PR:N/UI:R/S:C/C:H/I:H/A:H