EUVD-2026-74522
GHSA-ph55-qhgc-qr3g
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remote crafted page needs no privileges but requires victim interaction (social engineering) so UI:R; sandbox escape crosses a trust boundary (S:C) with full code-execution impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Payments in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox-escaping remote code execution in Google Chrome's Payments component (versions prior to 153.0.8010.36) lets a remote attacker who successfully social-engineers a victim into visiting a crafted HTML page trigger a use-after-free and potentially run arbitrary code outside the renderer sandbox. Chromium rates the security severity 'High'; the supplied CVSS is 9.6 reflecting scope change and full CIA impact. …
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 actively load an attacker-controlled crafted HTML page that exercises the Chrome Payments component, and the description explicitly states a social-engineering step is needed to lure the user - so exploitation is gated by user interaction (UI:R) even though no authentication is required (PR:N). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and point to lower real-world urgency than the 9.6 base score alone suggests. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Update Google Chrome to 153.0.8010.36 or later (Vendor-released patch: 153.0.8010.36) via the Stable channel update; on managed fleets, force a restart so the pending update applies, since Chrome staging can leave users on the vulnerable build until relaunch. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, issue urgent notification to all users and IT personnel regarding this critical vulnerability and direct immediate deployment of Chrome version 153.0.8010.36 or later through your patch management system, prioritizing executive and sensitive user populations. …
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 allShare
External POC / Exploit Code
Leaving vuln.today