CVE-2026-11673: Use after free in InterestGroups in Google Chrome prior to 149
Use after free in InterestGroups in Google Chrome prior to 149.0.7827.103 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.103
- Affected Products
- 1
HarborGuard Analysis
Synopsis
A use-after-free vulnerability in the InterestGroups component of Google Chrome prior to version 149.0.7827.103 allows a remote attacker to execute arbitrary code inside the browser sandbox by tricking a user into visiting a crafted HTML page. The attack is reachable over the network, requires no authentication, but does require the victim to load the malicious page. Successful exploitation gives an attacker arbitrary code execution within the Chrome sandbox, which can serve as a stepping stone to further compromise. A patched-image rebuild at version 149.0.7827.103 is available on HarborGuard for environments running an affected version of Chrome.
HarborGuard Coverage
Detection of CVE-2026-11673 is available across every HarborGuard environment; the CVE is ingested from upstream feeds within minutes of publication and matched against customer images in registries and CI/CD pipelines, including custom-built images that bundle a Chrome or Chromium binary.
AvailableHarborGuard scores this vulnerability at CVSS 8.8 (High) and surfaces it with that severity weighting in each customer's triage queue; per-environment compliance policy rules can further elevate priority and route the finding to the appropriate team inbox within each organization.
AvailableA patched-image rebuild at Chrome 149.0.7827.103 becomes available on HarborGuard for any environment where an affected version is detected. For customers who opt into auto-remediation, HarborGuard triggers a rebuild, runs a regression test suite, and opens a pull request against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker delivers the exploit over the network; the target Chrome instance must be reachable in the sense that the user browses to an attacker-controlled or compromised URL.
- AuthenticationNot required
No account, credential, or session token is needed; any unauthenticated remote party can serve the malicious page.
- Victim interactionRequired
The victim must navigate to or be redirected to a crafted HTML page, making this a classic drive-by or social-engineering scenario.
- Attack complexityDetail
Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, specific memory layouts, or other variable environmental factors.
Blast Radius
- The attacker executes arbitrary code inside the Chrome renderer sandbox, gaining control of the sandboxed process.
- Confidential data accessible to the renderer, such as in-page credentials, session tokens, and DOM content, is exposed to the attacker.
- The attacker can modify page content and in-browser state, enabling further phishing, credential harvesting, or data tampering within the session.
- While the initial compromise is sandbox-constrained, arbitrary code execution inside the sandbox is a well-established first step toward full sandbox escape and host-level access.
How HarborGuard Handles This
Available on HarborGuard: any image that bundles a Chrome or Chromium binary below version 149.0.7827.103 is flagged immediately upon ingestion of the CVE record, with no manual configuration required. For customers who opt into auto-remediation, HarborGuard rebuilds the image at the fixed version, runs a regression test suite, and opens a pull request against affected workloads; for High-severity issues, the median time from CVE publication to a merged patch PR in environments with auto-remediation enabled is around 90 minutes. For environments where auto-remediation is not enabled, the finding is surfaced in the triage dashboard with remediation guidance pointing to the 149.0.7827.103 upgrade. Where compliance policy permits, network-policy controls that restrict which internal workloads can spawn or embed a Chrome process can serve as a compensating control until the rebuild is deployed.
Fix available
- Google / Chrome< 149.0.7827.103 (from 149.0.7827.103)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H