ChromeWeb browser · Google
CVE-2026-0906
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 · uneditedIncorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: Low)
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 · moderate confidenceThis is a URL bar spoofing vulnerability in Google Chrome for Android. A remote attacker can craft a malicious HTML page that causes the Omnibox (URL bar) to display a different URL than the one the user is actually visiting. This enables phishing attacks by making users believe they are on a legitimate site when they are not. The vulnerability exists in versions prior to 144.0.7559.59.
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.59< 144.0.7559.60CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed Chrome version on AndroidOpen Google Chrome app, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed at the top.Affected if Version number is lower than 144.0.7559.59 (or 144.0.7559.60 depending on the specific patch level in use)
-
Verify Chrome update availabilityOpen Google Play Store app, search for Google Chrome, and check if an update is available. Alternatively, in Chrome go to Settings > Help > About Chrome and see if it prompts for an update.Affected if An update is available, indicating the installed version is older than the current stable release
-
Confirm Android platform is targetedThis vulnerability specifically affects Google Chrome on Android. Verify the affected app is Google Chrome (com.android.chrome) and not a different browser.Affected if The app in use is Google Chrome on Android and the version is below 144.0.7559.59
A user is affected if Google Chrome for Android is installed and the version number is less than 144.0.7559.59, making the Omnibox susceptible to spoofing via crafted HTML pages.
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.59144.0.7559.60
Update Google Chrome for Android to version 144.0.7559.59 or later to remediate this vulnerability. Users should be cautious about trusting the URL bar when visiting untrusted sites.
Chrome Android 144.0.7559.59 or later
- Open Google Play Store on the Android device
- Search for Google Chrome
- Tap Update to install version 144.0.7559.59 or later
- Alternatively, ensure automatic updates are enabled in Play Store settings to receive future security patches
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-0906 — 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-0906 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