Inappropriate Implementation in Payments in Google Chrome for Android

Publication date: 2026-06-04

Last updated on: 2026-06-08

Assigner: Chrome

Description

Inappropriate implementation in Payments in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to perform domain spoofing via a crafted HTML page. (Chromium security severity: Medium)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-04

Last Modified

2026-06-08

Generated

2026-07-15

AI Q&A

2026-06-05

EPSS Evaluated

2026-07-14

NVD

CVE-2026-11019

EUVD

EUVD-2026-34468

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
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.
CWE-290	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

Executive Summary

This vulnerability is an inappropriate implementation in the Payments feature of Google Chrome on Android versions prior to 149.0.7827.53. It allows a remote attacker who has already compromised the renderer process to perform domain spoofing by using a specially crafted HTML page.

Impact Analysis

The vulnerability can allow an attacker to spoof domains within the Payments feature, potentially misleading users into believing they are interacting with a legitimate site when they are not. This could lead to fraudulent transactions or theft of sensitive payment information if the attacker exploits the spoofing successfully.

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

0/70