ChromeWeb browser · Google
CVE-2026-0901
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 · uneditedInappropriate implementation in Blink in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: High)
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 confidenceA UI spoofing vulnerability in Google Chrome for Android's Blink rendering engine prior to version 144.0.7559.59 allows remote attackers to craft malicious HTML pages that can misrepresent the browser's UI, potentially tricking users into interacting with fraudulent interface elements.
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
< 144.0.7559.59CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the browser productVerify the browser is Google Chrome for Android, not Chrome for iOS, Chromium-based browsers, or desktop Chrome. Check the app name and package identifier in the device settings under Apps.Affected if The browser is Google Chrome for Android and the version is below 144.0.7559.59
-
Locate the version numberOpen Google Chrome for Android, tap the three-dot menu, go to Settings, then tap About Chrome to display the current version number.Affected if The displayed version is a number less than 144.0.7559.59 (for example, 144.0.7559.50 or lower)
-
Verify automatic updates are enabledIn Chrome for Android, tap the three-dot menu, go to Settings, then look for 'Auto-update' or check the device's Play Store settings to ensure Chrome receives automatic updates.Affected if Auto-update is disabled and manual version checks are not performed regularly
A user is affected if they are running Google Chrome for Android with a version number lower than 144.0.7559.59 on their device.
Generated from the published advisory. Verify against your own configuration.
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 · scoped144.0.7559.59
Update Google Chrome for Android to version 144.0.7559.59 or later. Organizations should ensure mobile devices have automatic updates enabled or push the updated browser version through their mobile device management (MDM) systems.
Chrome 144.0.7559.59 (Android)
- Open the Google Play Store app on the Android device
- Search for "Google Chrome" in the Play Store
- Tap on Google Chrome from the search results
- If an update is available, tap the "Update" button to install version 144.0.7559.59 or later
- Alternatively, ensure auto-updates are enabled: Open Play Store > Profile icon > Settings > Network preferences > Auto-update apps > Select "Over any network" or "Over Wi-Fi only"
- After updating, verify the version by opening Chrome > Settings > About Chrome to confirm version 144.0.7559.59 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0901 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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