CVE-2026-107808

Nginx UI: Authentication bypass: password login does not enforce a passkey-only second factor (2FA bypass)

func (u *User) EnabledOTP() bool     { return len(u.OTPSecret) != 0 }
func (u *User) EnabledPasskey() bool { /* true if a passkey row exists */ }
func (u *User) Enabled2FA() bool     { return u.EnabledOTP() || u.EnabledPasskey() }

func (u *User) AfterFind(_ *gorm.DB) error {
    u.EnabledTwoFA = u.Enabled2FA() // exposed to the UI as `enabled_2fa`
    return nil
}

u, err := user.Login(json.Name, json.Password)
...
if u.EnabledOTP() {                       // <-- only TOTP is enforced
    if json.OTP == "" && json.RecoveryCode == "" {
        c.JSON(http.StatusOK, LoginResponse{Message: "The user has enabled 2FA", Code: Enabled2FA}) // 199
        user.BanIP(clientIP)
        return
    }
    if _, err = user.VerifyOTP(u, json.OTP, json.RecoveryCode); err != nil { /* ... */ }
    secureSessionID = user.SetSecureSessionID(u.ID)
}

// Passkey-only accounts fall through to here and receive a full session token:
accessToken, err := user.GenerateJWT(u)

{"enabled":true,"otp_status":false,"passkey_status":true, ...}

HTTP 200
{"message":"ok","code":200,"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...."}

HTTP 200
{"message":"The user has enabled 2FA","code":199}

• Any account protected only by a passkey is reduced to password-only
  authentication. An attacker who obtains the password (phishing, reuse, leak)
  gains full access despite the registered security key.
• In nginx-ui all authenticated users are effectively administrators and the
  terminal feature grants a host shell, so account takeover leads to full
  control of the managed nginx instance / host.
• Users are given a false sense of security: the UI shows the account as
  2FA-enabled while the second factor is not enforced at login.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-107808 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.9.10-0.20260728074558-95cd21b70814); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

• Gate the second-factor decision on u.Enabled2FA() (not u.EnabledOTP()) in
  Login, in both SSO callbacks, and in RequireSecureSession().
• For a passkey-only user logging in with a password, return a
  "passkey assertion required" challenge and complete login only after a
  successful WebAuthn assertion (the begin_passkey_login / finish_passkey_login
  flow already exists and should be required as the second step).
• Centralize session-token issuance so no login entry point can skip the 2FA
  decision.

1. What is CVE-2026-107808? CVE-2026-107808 is a high-severity improper authentication vulnerability in github.com/0xJacky/Nginx-UI (go), affecting versions >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074558-95cd21b70814. It is fixed in 1.9.10-0.20260728074558-95cd21b70814. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-107808? CVE-2026-107808 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/0xJacky/Nginx-UI are affected by CVE-2026-107808? github.com/0xJacky/Nginx-UI (go) versions >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074558-95cd21b70814 is affected.
4. Is there a fix for CVE-2026-107808? Yes. CVE-2026-107808 is fixed in 1.9.10-0.20260728074558-95cd21b70814. Upgrade to this version or later.
5. Is CVE-2026-107808 exploitable, and should I be worried? Whether CVE-2026-107808 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-107808 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-107808? Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074558-95cd21b70814 or later.

Other vulnerabilities in github.com/0xJacky/Nginx-UI