EUVD-2026-42479
GHSA-mm39-x96q-96j9
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page needs only that the victim navigate to it (AV:N/AC:L/PR:N/UI:R); code runs in the renderer with no scope change (S:U) but high memory-corruption impact (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
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)
AnalysisAI
Remote code execution in Google Chrome desktop before 150.0.7871.115 stems from a use-after-free in the InterestGroups component (the Protected Audience / FLEDGE ad-auction API of Privacy Sandbox), letting a remote attacker run arbitrary code within the renderer sandbox by luring a victim to a crafted HTML page. Google rates the Chromium severity High, and the CVSS 8.8 reflects network-reachable, low-complexity, unauthenticated exploitation gated only by user interaction (visiting a page). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the victim to visit or load attacker-controlled content that exercises Chrome's InterestGroups / Protected Audience (FLEDGE) ad-auction code path - the crafted HTML page is the trigger, and UI:R in the CVSS vector confirms user interaction (navigating to the page) is mandatory. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 8.8) indicates a network-reachable, low-complexity bug needing no privileges but requiring user interaction, with high confidentiality/integrity/availability impact but no scope change - consistent with code execution confined to the renderer sandbox rather than a full host compromise. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that abuses the Protected Audience InterestGroups logic to trigger the use-after-free and then delivers it via phishing, a malicious ad, or a compromised site. When a victim running a pre-150.0.7871.115 Chrome visits the page (satisfying the UI:R requirement), the attacker corrupts renderer heap memory to execute arbitrary code within the browser sandbox. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.115 or later on all desktop platforms via the Chrome Releases stable-channel advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01162222768.html); relaunch the browser to apply the update since Chrome stages it in the background. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Audit all endpoints and identify systems running Chrome versions before 150.0.7871.115; notify users of mandatory update requirement. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-416 – Use After Free
View allSame technique Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today