CVE-2026-11286

Analyzed Analyzed - Analysis Complete

Insufficient Input Validation in Chrome Wallet Leads to UI Spoofing

Publication date: 2026-06-05

Last updated on: 2026-06-09

Assigner: Chrome

Description

Insufficient validation of untrusted input in Wallet in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-05

Last Modified

2026-06-09

Generated

2026-07-15

AI Q&A

2026-06-05

EPSS Evaluated

2026-07-14

NVD

CVE-2026-11286

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 149.0.7827.53 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-20	The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-451	The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.

Attack-Flow Graph

Executive Summary

This vulnerability involves insufficient validation of untrusted input in the Wallet feature of Google Chrome versions prior to 149.0.7827.53. It allows a remote attacker who has compromised the renderer process to perform UI spoofing by using a crafted HTML page.

Impact Analysis

The vulnerability can impact users by enabling an attacker to spoof the user interface, potentially misleading users into interacting with deceptive content. This could lead to phishing or other social engineering attacks if users are tricked into providing sensitive information.

Compliance Impact

This vulnerability involves insufficient validation of untrusted input in Google Chrome's Wallet feature, allowing UI spoofing by a remote attacker who has compromised the renderer process.

The impact is limited to integrity (UI spoofing) without direct confidentiality or availability compromise, and it has a low severity rating.

Based on the available information, there is no direct indication that this vulnerability leads to unauthorized access to personal data or protected health information, which are critical factors for compliance with standards like GDPR or HIPAA.

Therefore, this vulnerability is unlikely to have a significant direct effect on compliance with common data protection regulations such as GDPR or HIPAA.

Hi! I’m here to help you understand CVE-2026-11286. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70