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

Severity: high (CVSS 8.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-10-09 · updated 2026-10-20
Weakness: CWE-352

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.

Affected products

0xJacky nginx-ui: from 2.0.0 before 2.5.0 — fixed in 2.5.0

How to fix

Upgrade to a fixed version: 0xJacky nginx-ui 2.5.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-107809 or the next vulnerability affects your stack