# CVE-2026-107813: Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up > Authenticated users with stolen JWTs can bypass OTP step-up to modify cluster nodes and restart Nginx services in Nginx UI. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** GHSA-h246-wpgf-vmq5, GO-2026-6706 ## What is CVE-2026-107813? CVE-2026-107813 is a high-severity missing authorization vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, the api/cluster router exposes node and namespace mutation operations and cluster-wide Nginx reload or restart operations with AuthRequired but without RequireSecureSession. An authenticated OTP-enabled user possessing a stolen or persisted JWT can therefore perform node CRUD, read or replace node credentials, change namespaces, and invoke nodes/reload_nginx or nodes/restart_nginx without a fresh second-factor step-up. This issue is an incomplete fix for CVE-2026-84315 and is fixed in version 2.5.0. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2026-107813? 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-107813? Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074433-a3999bd78a3b or later. ## Is CVE-2026-107813 being exploited? There is no known exploitation of CVE-2026-107813 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-107813 and fix it if it is affected. What it is: CVE-2026-107813 is a high-severity missing authorization vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107813 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-107813/ (Markdown: https://insights.sbomify.com/CVE-2026-107813/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107813 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107813 - OSV: https://osv.dev/vulnerability/CVE-2026-107813 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107813/ Summaries are generated and may contain mistakes; the official description above is the record.