dbcve.org
ChromeWeb browser · Google

CVE-2026-11019

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a domain spoofing vulnerability in Google Chrome's Payments component on Android. A remote attacker with a compromised renderer process could craft HTML to deceive users about the actual domain they're visiting, potentially redirecting payments or stealing credentials. The fix is available in Chrome Android version 149.0.7827.53 and later.

MitigationUpdate Google Chrome for Android to version 149.0.7827.53 or later. Organizations managing mobile devices should use MDM to verify and enforce the browser update across all managed Android devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 149.0.7827.53

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Google Chrome is installed on the Android device
    Navigate to Settings > Apps on the Android device and look for Google Chrome in the app list, or check the app version info directly from the Chrome app menu > Help & Feedback > Version
    Affected if Chrome browser is present on the device
  2. Determine the installed Chrome version
    Open Chrome app, tap the three-dot menu, go to Help & Feedback, then tap Version to display the full version string (e.g., 149.0.7827.53)
    Affected if Version number is displayed and can be compared to the threshold
  3. Compare installed version against the affected range
    Compare the four-part version number shown (e.g., 149.0.7827.53) to the threshold. The format is major.minor.build.patch. Check if the major version is less than 149, or if major equals 149 but minor is less than 7827, etc.
    Affected if Installed version is below 149.0.7827.53 (e.g., 148.x.x.x or any earlier major version)
  4. Verify the Payments feature is accessible
    On Android Chrome, attempt to access payment methods by visiting a site that supports Payment Request API, or navigate to Chrome Settings > Payment methods (if available in that version)
    Affected if The Payments UI is accessible and the user enters payment information in Chrome

The user is affected if Chrome on Android is installed with a version prior to 149.0.7827.53 and they use the browser's payment features to enter or manage payment information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome for Android to version 149.0.7827.53 or later. Organizations managing mobile devices should use MDM to verify and enforce the browser update across all managed Android devices.

Recommended fix High confidence

Chrome 149.0.7827.53 for Android (or later stable release)

  1. Open the Google Play Store app on the Android device
  2. Search for 'Google Chrome' or locate it in the installed apps list
  3. Tap the 'Update' button if an update is available
  4. Verify the update completed successfully
  5. Confirm the installed version is 149.0.7827.53 or later by going to Settings > Apps > Chrome > Version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11019 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data