# CVE-2026-107809: Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

> Attackers can trick administrators into modifying Nginx configurations via CSRF due to missing token validation on management APIs.

- **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:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-33rr-wq23-g6gg, GO-2026-6703

## What is CVE-2026-107809?

CVE-2026-107809 is a high-severity vulnerability in 0xJacky nginx-ui, published on 9 Oct 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

Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, AuthRequired accepts a browser-managed token cookie as an API credential after the front end stores the JWT in that cookie. Because management endpoints do not universally require a CSRF token or perform Origin or Referer validation, a remote attacker can induce a logged-in administrator's browser to submit authenticated cross-site state-changing requests, including POST /api/configs. The attack requires an administrator account without OTP/Passkey or a target endpoint that does not require secure-session proof. The attacker cannot read the cross-origin response but can modify Nginx configuration, trigger reloads, or invoke other management operations reachable with the victim's session. This issue is fixed in version 2.5.0.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074433-a3999bd78a3b |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074433-a3999bd78a3b |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074433-a3999bd78a3b |

Products: Nginxui Nginx Ui.

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

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074433-a3999bd78a3b or later.

## Is CVE-2026-107809 being exploited?

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

## Other vulnerabilities in 0xJacky nginx-ui

- [CVE-2026-33032](https://insights.sbomify.com/CVE-2026-33032/): Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover (critical 9.8)
- [CVE-2026-27944](https://insights.sbomify.com/CVE-2026-27944/): Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure (critical 9.8)
- [CVE-2024-23827](https://insights.sbomify.com/CVE-2024-23827/): Nginx-UI arbitrary file write through the Import Certificate feature (critical 9.8)
- [CVE-2026-107806](https://insights.sbomify.com/CVE-2026-107806/): Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite (critical 9.4)
- [CVE-2026-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107809 is a high-severity vulnerability in 0xJacky nginx-ui, published on 9 Oct 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-107809 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074433-a3999bd78a3b
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074433-a3999bd78a3b
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074433-a3999bd78a3b

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-107809/ (Markdown: https://insights.sbomify.com/CVE-2026-107809/index.md)
```

## Sources

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

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