# CVE-2026-22559: Open redirect in UniFi Network Server

> Attackers can gain unauthorized account access by tricking users into clicking malicious links due to improper input validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-8m5g-mp2m-6hp8

## What is CVE-2026-22559?

CVE-2026-22559 is a high-severity vulnerability in Ubiquiti Inc UniFi Network Server, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-22559?


## How do I fix CVE-2026-22559?

No fix has been published for CVE-2026-22559 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22559 being exploited?

There is no known exploitation of CVE-2026-22559 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22559 and fix it if it is affected.

What it is: CVE-2026-22559 is a high-severity vulnerability in Ubiquiti Inc UniFi Network Server, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22559 in the wild and no public exploit code.

Affected product: Ubiquiti Inc UniFi Network Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22559/ (Markdown: https://insights.sbomify.com/CVE-2026-22559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22559
- OSV: https://osv.dev/vulnerability/CVE-2026-22559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22559/
Summaries are generated and may contain mistakes; the official description above is the record.