---
title: "CVE-2026-107813: Nginx UI - Authentication Bypass"
description: "Nginx UI 2.0.0 to 2.5.0 contains a broken authentication caused by missing RequireSecureSession enforcement on api/cluster router, letting authenticated OTP-enabled users with stolen JWT perform node and cluster operations without second-factor, exploit requires valid JWT token."
url: https://panop.io/threat-heartbeat/CVE-2026-107813/
---

# CVE-2026-107813 Nginx UI - Authentication Bypass

Nginx UI 2.0.0 to 2.5.0 contains a broken authentication caused by missing RequireSecureSession enforcement on api/cluster router, letting authenticated OTP-enabled users with stolen JWT perform node and cluster operations without second-factor, exploit requires valid JWT token.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.30% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-107813)

## Details

Type

Authentication Bypass

Impact

Broken Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

9 October 2026

Updated

15 October 2026

Weakness

[CWE-862](https://cwe.mitre.org/data/definitions/862.html)

## Vendor fix

Update to version 2.5.0 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-107813](https://nvd.nist.gov/vuln/detail/CVE-2026-107813)
- [https://github.com/0xJacky/nginx-ui/commit/a3999bd78a3b97ab22e6b5e9fd478ac57598a954](https://github.com/0xJacky/nginx-ui/commit/a3999bd78a3b97ab22e6b5e9fd478ac57598a954)
- [https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0](https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0)
- [https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-h246-wpgf-vmq5](https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-h246-wpgf-vmq5)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)