EUVD-2026-42455
GHSA-9rvx-ch9v-838r
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page needs user interaction (UI:R) but no auth (PR:N); high C/I/A reflect full code execution within the unchanged-scope renderer sandbox.
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 Forms 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
Sandboxed remote code execution in Google Chrome versions prior to 150.0.7871.115 stems from a use-after-free in the Forms component, allowing a remote attacker to run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. The flaw carries a High Chromium severity rating and CVSS 8.8; Google has shipped a stable-channel fix, but 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 or be navigated to an attacker-crafted HTML page in an unpatched Chrome build prior to 150.0.7871.115 (UI:R in the CVSS vector confirms required user interaction); no authentication is needed (PR:N). … 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, score 8.8) indicates network-reachable, low-complexity, unauthenticated exploitation requiring only that a user visit a malicious page - a realistic condition for a browser. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a malicious HTML page containing JavaScript that manipulates form elements to trigger the use-after-free, then lures a victim to visit it via phishing, a malicious ad, or a compromised site (UI:R - the user must open the page). Successful exploitation grants arbitrary code execution inside the Chrome renderer sandbox; to reach the host, the attacker would then need to chain a separate sandbox-escape vulnerability. … |
| Remediation | Update Google Chrome to version 150.0.7871.115 or later on all desktop platforms; this is a vendor-released patch delivered through Chrome's automatic update channel, so verify the update applied by opening chrome://settings/help and relaunching the browser to complete installation, as staged updates do not take effect until restart. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Audit Chrome deployment across endpoints and identify systems running versions prior to 150.0.7871.115. …
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