EUVD-2026-65837
GHSA-wj5w-x49q-8g6h
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Renderer pre-compromise is a significant chained prerequisite that warrants AC:H; UI:R retained for mandatory social engineering; C:L only, no I or A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Improper input validation in Input in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Web origin policy bypass in Google Chrome before 152.0.7977.65 exploits improper input validation (CWE-20) in the browser's Input component, allowing a remote attacker who has already compromised the renderer process to circumvent same-origin protections via a crafted HTML page combined with social engineering. The confidentiality impact is limited (CVSS C:L) with no integrity or availability consequence, and the Chromium team rates this Medium severity. …
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 two concurrent pre-conditions: first, the attacker must have already achieved code execution within the Chrome renderer process (e.g., via a separate, unpatched renderer vulnerability); second, the victim must be socially engineered through a crafted HTML page - user interaction is not optional. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.3 Medium score reflects a constrained but real attack surface: while network-reachable (AV:N) with no authentication requirement (PR:N), exploitation demands two sequential pre-conditions - prior renderer process compromise and successful social engineering of the victim (UI:R) - which substantially elevates real-world difficulty beyond what the AC:L metric suggests. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has separately compromised a Chrome renderer process - for example via an unpatched renderer vulnerability - serves the victim a crafted HTML page that uses social engineering to prompt user interaction. The improper input validation flaw is then triggered, allowing the attacker to bypass the web origin policy from within the compromised renderer and exfiltrate limited cross-origin data. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later, as documented in the vendor's stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today