dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-22559

HIGH · 8.8 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
An Improper Input Validation vulnerability in UniFi Network Server may allow unauthorized access to an account if the account owner is socially engineered into clicking a malicious link. Affected Products: UniFi Network Server (Version 10.1.85 and earlier) Mitigation: Update UniFi Network Server to Version 10.1.89 or later.

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 confidence

Improper input validation in UniFi Network Server allows unauthorized account access when a user is socially engineered into clicking a malicious link, potentially enabling session hijacking or authentication bypass.

MitigationUpdate UniFi Network Server to Version 10.1.89 or later to remediate the input validation vulnerability.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Identify UniFi Network Server installation
    Locate the UniFi Network Server installation. On Linux, check /usr/lib/unifi or /opt/UniFi. On Windows, check Program Files or the installation directory. On macOS, check /Applications/UniFi or ~/Library/Application Support/UniFi.
    Affected if UniFi Network Server is not installed on the system
  2. Determine installed UniFi Network Server version
    Access the UniFi Network web interface and navigate to Settings > System > About, or check the version file in the installation directory (version.properties or similar). Alternatively, use the command line: java -jar /path/to/lib/UniFi.jar --version or check the changelog file.
    Affected if Unable to retrieve the installed version number
  3. Compare version against fixed release
    Compare the installed version number to the fixed version 10.1.89. Versions lower than 10.1.89 are affected. Note that major version branches (e.g., 7.x, 8.x) are separate from the 10.x branch; ensure comparison is within the same major version line.
    Affected if Installed version is below 10.1.89 within the same major version branch
  4. Assess web interface exposure
    Determine if the UniFi Network Controller web interface is accessible from untrusted networks. Check network firewall rules, port forwarding configurations, or VPN access policies that expose ports 443, 8080, or 8443 to the internet or untrusted LAN segments.
    Affected if The UniFi web interface is exposed to untrusted networks without additional authentication protections

A user is affected if UniFi Network Server is installed with a version lower than 10.1.89 and the web interface is network-accessible, enabling the social engineering attack vector.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update UniFi Network Server to Version 10.1.89 or later to remediate the input validation vulnerability.

Recommended fix High confidence

UniFi Network Server 10.1.89 or later

  1. 1. Back up the current UniFi Network Server configuration and data before starting the upgrade process.
  2. 2. Download UniFi Network Server version 10.1.89 or later from the official Ubiquiti Downloads page.
  3. 3. Stop the currently running UniFi Network Server service.
  4. 4. Install the downloaded UniFi Network Server update (version 10.1.89 or later).
  5. 5. Start the UniFi Network Server service after installation completes.
  6. 6. Verify the server is running the updated version by checking the server console or about page.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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