CVE-2026-84315: Nginx UI OTP secure-session step-up is missing on sensitive mutation routes
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, Nginx UI does not apply RequireSecureSession to multiple authenticated mutation routes even though OTP-enabled users are expected to present a fresh X-Secure-Session-ID for sensitive actions. A stolen authenticated session can therefore create or alter automatic backups, DNS credentials and records, certificates and ACME users, Nginx control settings, and site or stream automation without completing the OTP or passkey step-up. This issue is fixed in version 2.4.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Nginx UIto a version that resolves this vulnerability.Fixed in 2.4.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Deployments of Nginx UI before version 2.4.1 are affected where an attacker can obtain an authenticated user session. OTP-enabled users are specifically impacted because sensitive mutation routes may not require the expected fresh secure-session step-up.
What does an attacker need to exploit it?
The attacker needs a stolen authenticated session. They do not need to complete the OTP or passkey step-up for the affected sensitive actions.
What actions could be performed with a stolen session?
An attacker could create or modify automatic backups, DNS credentials and records, certificates and ACME users, Nginx control settings, and site or stream automation.
What should teams do to remediate the issue?
Upgrade Nginx UI to version 2.4.1, which fixes the missing RequireSecureSession protection on the affected routes.
How can teams assess possible impact before upgrading?
Review whether Nginx UI instances are running a version earlier than 2.4.1 and investigate sensitive configuration changes made through authenticated sessions, particularly changes involving backups, DNS, certificates, Nginx controls, and automation.