HIGH 8.8

CVE-2026-15133: Chrome Use-After-Free in InterestGroups (CVSS 8.8)

Google Chrome versions before 150.0.7871.115 contain a use-after-free vulnerability in the InterestGroups feature. An attacker can craft a malicious HTML page that, when opened in an affected browser, triggers the flaw to execute arbitrary code within the Chrome sandbox. The vulnerability requires user interaction (visiting a malicious page) but poses a high risk due to the ease of exploitation and the potential for sandbox escape or data theft.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-416
Affected products
1 configuration(s)
Published / Modified
2026-07-08 / 2026-07-10

NVD description (verbatim)

Use after free in InterestGroups in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-15133 is a use-after-free bug (CWE-416) in Chrome's InterestGroups implementation. Use-after-free vulnerabilities occur when a program accesses memory that has already been freed, allowing attackers to overwrite freed memory regions or trigger unexpected behavior. In this case, improper lifecycle management of InterestGroups objects permits remote code execution with High severity. The vulnerability is reachable via malicious HTML delivered over the network, requiring only user action (page navigation) to trigger. Execution occurs within the browser sandbox, which provides a containment layer but does not eliminate the risk of further exploitation.

Business impact

A successful exploitation chain could allow attackers to steal sensitive user data (credentials, browsing history, saved passwords) or use the sandbox as a pivot point for additional attacks. For organizations, widespread Chrome exploitation increases endpoint compromise risk, particularly if users cannot be prevented from visiting untrusted sites. Incident response and credential rotation costs may follow successful attacks. The high CVSS score (8.8) reflects the combination of network accessibility, low attack complexity, and confidentiality/integrity/availability impact.

Affected systems

Google Chrome prior to version 150.0.7871.115 is affected across all platforms (Windows, macOS, Linux). The vulnerability impacts standard Chrome installations and Chromium-based browsers that include the InterestGroups feature. Enterprise Chrome deployments managed via policy may have different update timelines. Verify the exact version deployed in your environment—Chrome auto-updates, but organizations with managed deployments should confirm rollout status.

Exploitability

Exploitability is high. The attack requires only a crafted HTML page and user interaction (visiting a link or page), both low barriers. No special privileges or complex setup are needed on the attacker side. The flaw is reachable remotely via any network path to a user's browser. However, successful exploitation depends on the victim's browser version and whether the InterestGroups feature is enabled in their configuration. Public exploitation activity has not been confirmed in the CISA KEV catalog, but the vulnerability's inherent simplicity suggests rapid weaponization is likely once disclosure details circulate.

Remediation

Update Chrome to version 150.0.7871.115 or later immediately. Chrome auto-updates, but users should verify their version in Settings > About Google Chrome. For enterprise deployments, push the update via your configuration management system and verify adoption across endpoints. No workarounds mitigate the vulnerability short of disabling the browser or blocking untrusted sites—patching is the only reliable solution.

Patch guidance

Users should enable automatic updates and confirm they are running Chrome 150.0.7871.115 or newer. Enterprise administrators should deploy the patch through their device management policies (Intune, JAMF, etc.) and track compliance metrics. Verify patch success by checking browser version numbers in your MDM console. If manual Chrome deployment is used, manually trigger updates or queue the installer. Prioritize this patch above regular update schedules due to the high severity and lack of workarounds.

Detection guidance

Endpoint detection should focus on identifying unpatched Chrome versions through inventory scans or MDM reporting. Monitor for unusual child processes spawned by chrome.exe (possible sandbox escape attempts) or abnormal memory access patterns. Network-level detection is limited since the attack involves legitimate HTML; however, you may log attempts to visit known malicious domains hosting exploit kits. Hunt for indicators of lateral movement or credential theft following unpatched Chrome usage on sensitive systems.

Why prioritize this

This vulnerability scores 8.8 CVSS (High severity) with no KEV designation but clear exploitability. Prioritize it for patching within 1–2 weeks, especially for users handling sensitive data or accessing internal resources. The low attack complexity and network accessibility, combined with sandbox containment bypass potential, make it a critical endpoint risk. Organizations with user populations visiting untrusted sites should treat it as urgent.

Risk score, explained

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) yields a score of 8.8 (High). Network accessibility (AV:N) and low attack complexity (AC:L) maximize the likelihood of exploitation. Lack of privileges required (PR:N) means any user can be targeted. User interaction (UI:R) is the only limiting factor—the attacker must trick the user into visiting a malicious page. Scope unchanged (S:U) means impact is limited to the Chrome process. High ratings for confidentiality, integrity, and availability reflect the sandbox execution context and potential for information leakage or code execution.

Frequently asked questions

Will Chrome auto-update fix this for me?

Yes, Chrome auto-updates typically deliver security patches within hours to days of release. You can speed up the process by going to Settings > About Google Chrome, which forces an immediate check and restart. Verify you're on version 150.0.7871.115 or later.

What happens if an attacker exploits this—can they escape the Chrome sandbox?

Exploitation itself occurs within the sandbox, which provides some containment. However, the vulnerability's severity suggests potential for further escalation or data theft from browser-level resources (cookies, passwords, browsing history). Assume that successful exploitation could lead to account compromise or lateral movement if the victim's system is on a network with other sensitive systems.

Do I need to worry about this if my users only visit trusted internal sites?

You should still patch promptly, as users may inadvertently visit untrusted sites or receive malicious links in email. Additionally, compromised legitimate websites can serve exploits. Patching is simpler and faster than preventing all possible attack vectors.

Is there a workaround if I cannot patch immediately?

No fully effective workaround exists. You can disable the InterestGroups feature via policy (which may impact some ad-related functionality) or restrict browsing to trusted domains, but these are temporary measures. Patching within 1–2 weeks is the only reliable solution.

This analysis is based on publicly disclosed information as of the publication date. Exploit code and detailed attack vectors are intentionally omitted to avoid enabling active exploitation. Organizations should verify patch availability and compatibility with their deployment environment before rolling out updates. CVSS scores reflect base severity; actual organizational risk depends on system configuration, user behavior, and network posture. For the latest advisory details, consult Google's official Chrome security release notes. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).