Skip to main content

Google Chrome EUVDEUVD-2026-74412

| CVE-2026-87435 MEDIUM
Information Exposure (CWE-200)
2026-09-09 Chrome GHSA-2j27-2q88-8v7q
5.3
CVSS 3.1 · Vendor: Chrome
Share

Severity by source

Vendor (Chrome) PRIMARY
5.3 MEDIUM
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
vuln.today AI
5.3 MEDIUM

AC:H encodes renderer pre-compromise prerequisite; UI:R for crafted HTML; C:H for sensitive cross-origin data; I:N/A:N for read-only disclosure with no scope change.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
Sep 09, 2026 - 15:42 vuln.today
Patch available
Sep 09, 2026 - 01:03 EUVD
CVE Published
Sep 09, 2026 - 00:09 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 09, 2026 - 00:09 cve.org
MEDIUM 5.3

DescriptionCVE.org

Information leak in ControlledFrame 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

ControlledFrame in Google Chrome prior to 153.0.8010.36 exposes sensitive information to an attacker who has already achieved renderer process compromise, exploitable via a crafted HTML page (UI:R). This is a chained post-exploitation primitive rather than an initial access vector: it extends the damage of a separate renderer exploit by enabling cross-origin data exfiltration from the victim's session. …

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

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires two chained conditions: (1) The attacker must have already achieved code execution within Chrome's renderer process via a separate, independent vulnerability - this is a substantial prerequisite that limits the attack surface to scenarios where an active renderer exploit chain exists or is deployed. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 5.3 (Medium) vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N is well-calibrated: AC:H encodes the non-trivial prerequisite of a pre-compromised renderer, UI:R reflects victim interaction with a crafted HTML page, C:H captures the potential sensitivity of ControlledFrame-accessible data, and I:N/A:N correctly reflect a read-only disclosure impact with no scope change (S:U). … 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; this release is documented in the stable channel advisory at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html and can be applied via Chrome's built-in updater or enterprise deployment (GPO, SCCM, Workspace ONE). … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-74412 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy