EUVD-2026-74391
GHSA-43q8-2qf6-v2mg
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Renderer-compromise prerequisite justifies AC:H; no auth to Chrome required (PR:N); impact is confidentiality-only via DataTransfer data exposure with no integrity or availability effect.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
5DescriptionCVE.org
Incorrect authorization in DataTransfer in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Incorrect authorization in Chrome's DataTransfer API (prior to 153.0.8010.36) permits an attacker who has already achieved renderer process compromise to read sensitive data via a crafted HTML page. The flaw (CWE-863) bypasses intended access-control checks on clipboard or drag-and-drop data within the renderer context, enabling information disclosure rather than code execution. …
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 sequential conditions: first, the Chrome renderer process must already be compromised via a separate, independent vulnerability - this is the primary barrier. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real-world exploitation risk is meaningfully constrained by the prerequisite renderer compromise, making this a second-stage information-disclosure primitive rather than a standalone threat. … 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 | Upgrade Google Chrome to version 153.0.8010.36 or later, as confirmed by the official Chrome stable channel release advisory at chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.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-863 – Incorrect Authorization
View allShare
External POC / Exploit Code
Leaving vuln.today