CVE-2026-11019: Inappropriate implementation in Google Chrome
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)
AI Analysis
Technical Summary
This vulnerability arises from an inappropriate implementation in the Payments component of Google Chrome on Android versions before 149.0.7827.53. A remote attacker with control over the renderer process can exploit this flaw to spoof domains through a specially crafted HTML page. The issue is tracked as CVE-2026-11019 and is associated with CWE-290 (Authentication Bypass) and CWE-451 (User Interface Misrepresentation). The CVSS v3.1 base score is 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No known exploits in the wild have been reported. The vendor advisory URL points to a Chrome stable channel update announcement but does not explicitly confirm patch availability or remediation status for this specific issue.
Potential Impact
The vulnerability allows a remote attacker who has already compromised the renderer process to perform domain spoofing, potentially misleading users by misrepresenting the origin of web content. This impacts the integrity of the browsing experience but does not affect confidentiality or availability. No known active exploitation has been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html for current remediation guidance. Since this is a client-side vulnerability in Chrome on Android, users should update to version 149.0.7827.53 or later once confirmed by the vendor. Until then, no specific mitigation steps are provided by the vendor advisory.
CVE-2026-11019: Inappropriate implementation in Google 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 v3.1
Score 6.5medium
Affected software
pkg:github/chromium/chromiumRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from an inappropriate implementation in the Payments component of Google Chrome on Android versions before 149.0.7827.53. A remote attacker with control over the renderer process can exploit this flaw to spoof domains through a specially crafted HTML page. The issue is tracked as CVE-2026-11019 and is associated with CWE-290 (Authentication Bypass) and CWE-451 (User Interface Misrepresentation). The CVSS v3.1 base score is 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No known exploits in the wild have been reported. The vendor advisory URL points to a Chrome stable channel update announcement but does not explicitly confirm patch availability or remediation status for this specific issue.
Potential Impact
The vulnerability allows a remote attacker who has already compromised the renderer process to perform domain spoofing, potentially misleading users by misrepresenting the origin of web content. This impacts the integrity of the browsing experience but does not affect confidentiality or availability. No known active exploitation has been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html for current remediation guidance. Since this is a client-side vulnerability in Chrome on Android, users should update to version 149.0.7827.53 or later once confirmed by the vendor. Until then, no specific mitigation steps are provided by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Chrome
- Date Reserved
- 2026-06-04T17:06:30.671Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html","vendor":"Google"}]
Threat ID: 6a220819e29bf47b50dbb0f8
Added to database: 06/04/2026, 23:19:53 UTC
Last enriched: 06/12/2026, 09:55:25 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 45
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.