Skip to main content

Google Chrome Android EUVDEUVD-2026-74460

| CVE-2026-87624 MEDIUM
User Interface (UI) Misrepresentation of Critical Information (CWE-451)
2026-09-09 Chrome GHSA-x4mc-8mvw-5mq9
4.2
CVSS 3.1 · Vendor: Chrome
Share

Severity by source

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

Renderer compromise prerequisite justifies AC:H; UI spoofing yields only limited confidentiality impact; no availability mechanism described.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/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
Low
Integrity
None
Availability
Low

Lifecycle Timeline

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

DescriptionCVE.org

UI misrepresentation in Passwords in Google Chrome on on Android prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to spoof UI elements via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

UI spoofing in the Passwords component of Google Chrome on Android (versions prior to 153.0.8010.36) enables an attacker who has already compromised the renderer process to display falsified password-manager interface elements via a crafted HTML page. Exploitation is constrained by a hard prerequisite - a separate renderer compromise must precede this attack - and requires user interaction with the malicious page. …

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
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Two hard conditions must both be met: (1) the attacker must have already achieved code execution within Chrome's renderer process on the target Android device - this requires a separate renderer-level exploit (the renderer compromise is itself the primary prerequisite, reflected in AC:H); and (2) the target user must visit or load the attacker's crafted HTML page (UI:R). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment Real-world risk is materially lower than a network-delivered CVSS 4.2 might suggest in isolation. … 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 Vendor-released patch: Chrome 153.0.8010.36 for Android. … Detailed patch versions, workarounds, and compensating controls in full report.

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

Share

EUVD-2026-74460 vulnerability details – vuln.today

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