dbcve.org
ChromeWeb browser · Google

CVE-2026-5895

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 147.0.7727.55 or later.
See remediation →
61/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
Incorrect security UI in Omnibox in Google Chrome on iOS prior to 147.0.7727.55 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted domain name. (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 · high confidence

URL bar (Omnibox) spoofing vulnerability in Google Chrome on iOS allows a remote attacker to display misleading URL information in the address bar via a crafted domain name, potentially tricking users into believing they're on a different website.

MitigationUpdate Google Chrome on iOS to version 147.0.7727.55 or later to patch this vulnerability.

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:< 147.0.7727.55

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
Low
Integrity
None
Availability
Low

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

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. Verify Chrome is installed on iOS
    Look for the Google Chrome app icon on the device home screen, in a folder, or search for it in the iOS App Library
    Affected if Google Chrome app is present on the iOS device
  2. Find installed Chrome version on iOS
    Open Chrome app, tap the three-dot menu in the bottom-right corner, scroll down and tap Settings, tap Chrome at the top, and read the version number displayed under 'Chrome'
    Affected if Unable to locate or read the version number from Chrome settings
  3. Compare version to affected range
    Note the full version number shown (for example, it may appear as something like 147.0.7727.xx) and determine if it is less than 147.0.7727.55
    Affected if Installed version number is lower than 147.0.7727.55 or the version shown begins with a number less than 147

The user is affected if Google Chrome for iOS is installed and the displayed version is earlier than 147.0.7727.55, as this is the specific version range where the URL bar spoofing vulnerability exists.

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 147.0.7727.55 or later
Fixed in 147.0.7727.55
Interim mitigation

Update Google Chrome on iOS to version 147.0.7727.55 or later to patch this vulnerability.

Recommended fix High confidence

Chrome iOS 147.0.7727.55 or later

  1. Open the App Store on your iOS device
  2. Search for Google Chrome
  3. Tap Update to upgrade to version 147.0.7727.55 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing0.5 h
  • Review / QA0.5 h
2.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5895 — 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-5895 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