EUVD-2026-42488
GHSA-r7m5-ccww-9j78
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-delivered crafted page (AV:N) with no auth (PR:N) but mandatory payment UI gestures (UI:R) and a race/heap-grooming UAF (AC:H); successful exploitation yields full C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Payments in Google Chrome prior to 150.0.7871.115 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Heap corruption in Google Chrome's Payments component (versions prior to 150.0.7871.115) lets a remote attacker who lures a user into performing specific UI gestures potentially achieve code execution via a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 7.5, with a vendor patch already shipped in the July 2026 Stable channel update; no public exploit has been identified at time of analysis. …
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 open an attacker-controlled crafted HTML page AND to perform specific UI gestures that drive the Chrome Payments flow (per the description's 'convinced a user to engage in specific UI gestures') - the payment UI interaction is the concrete precondition, not merely visiting the page. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H yields 7.5 (High): network-reachable and unauthenticated (PR:N), but tempered by high attack complexity (AC:H) and required user interaction (UI:R), with full C/I/A impact if it lands. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page and, via phishing or a malicious ad, entices a victim to visit it and perform particular UI gestures within a payment-related flow. Those gestures trigger the use-after-free in the Payments component, corrupting the heap; with successful heap grooming the attacker aims to escalate from the crash to code execution in the browser context. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.115 or later via the Chrome Releases Stable channel update (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01162222768.html) and restart the browser to apply - enterprise fleets should push the update through their managed-update/Group Policy channel and force a relaunch, since Chrome only completes the swap after restart. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Deploy Chrome version 150.0.7871.115 or later to all managed endpoints via automatic updates or system administration tools. …
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