Vulnerabilities in pkg:golang/github.com/0xJacky/Nginx-UI

PACKAGE
Advisory Identifier: GHSA-vc32-4gwf-77xp
Advisory Summary

CVE-2026-84360 is a HIGH (CVSS 8.1) otp secure-session step-up can be vulnerability (CWE-288: Authentication Bypass Using an Alternate Path or Channel) affecting Nginx UI libraries in the Go ecosystem. The issue involves otp secure-session step-up can be bypassed via mcp configuration tools. Remediation is available by upgrading affected packages to version 1.9.10-0.20260703131214-23d1934099b0.

35 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/0xJacky/Nginx-UI

35 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/0xJacky/Nginx-UI. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-vc32-4gwf-77xp CVE-2026-84360 HIGH Nginx UI: OTP secure-session step-up can be bypassed via MCP configuration tools
GHSA-wq4w-vwvq-q3x9 CVE-2026-84321 MODERATE Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
GHSA-cf23-7qxj-xmhr CVE-2026-84316 HIGH Nginx UI: nginx config directive denylist (ValidateConfigFile) is bypassable via same-line ";" separation → authenticated directive injection (RCE on the official image)
GHSA-5v7c-xpfp-p65m CVE-2026-84315 HIGH Nginx UI OTP secure-session step-up is missing on sensitive mutation routes
GHSA-2gc7-j998-5xx6 CVE-2026-84314 HIGH Nginx UI: Account Takeover via Missing `RequireSecureSession` on User Management Endpoint
GHSA-9jww-cxg5-rj9m CVE-2026-84318 HIGH Nginx UI: MCP `nginx_config_add` Bypasses Directive Validation — Authenticated RCE
GHSA-76pm-mq2q-9gcr CVE-2026-84317 HIGH Nginx UI: MCP nginx_config_add skips config directive validation → authenticated nginx directive injection (RCE on the official image)
GHSA-jrq7-xrjx-pcfw CVE-2026-84320 MODERATE Nginx UI: Auto backup name allows path traversal outside validated storage path
GHSA-5r62-gj48-897x CVE-2026-84319 HIGH Nginx UI: MCP configuration tools bypass restricted directive validation and allow secondary authenticated users to execute NJS in Nginx worker context
GHSA-j3hg-9rp3-5hw9 CVE-2026-107805 HIGH Nginx UI: Unauthenticated signed-request body staging can exhaust temporary storage
GHSA-9h23-53f4-q947 CVE-2026-107804 MODERATE Nginx UI: Bundled reverse proxy can bypass IP allowlists and enable shared login lockout
GHSA-p393-cf76-4jmr CVE-2026-107806 CRITICAL Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite
GHSA-662p-52hx-cmh2 CVE-2026-107812 HIGH Nginx UI: Self-upgrade runs an unsigned binary verified only by a same-origin digest → RCE via a compromised mirror or MITM
GHSA-45gv-9wjv-xh7p CVE-2026-107808 HIGH Nginx UI: Authentication bypass: password login does not enforce a passkey-only second factor (2FA bypass)
GHSA-33rr-wq23-g6gg CVE-2026-107809 HIGH Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs
GHSA-h246-wpgf-vmq5 CVE-2026-107813 HIGH 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
GHSA-32gc-wf3m-78w9 CVE-2026-107811 HIGH 0xJacky/nginx-ui /api/nodes Leaks Cluster Node Tokens and Allows Cross-Node Impersonation as initUser
GHSA-pvgv-gcp7-v38g CVE-2026-107807 HIGH Nginx UI: Node Secret Credential Exposure via URL Query Parameter
GHSA-p8v3-89rh-jxc7 CVE-2026-107810 HIGH Nginx UI: Backup restore follows crafted symlinks into the live Nginx configuration path before restore flags are applied
GHSA-7jrr-xw9c-mj39 CVE-2026-42220 MODERATE Nginx-UI: Authenticated settings disclosure exposes node.secret and enables trusted-node authentication abuse, backup exfiltration, and restore-based nginx-ui state rollback
GHSA-fhh2-gg7w-gwpq CVE-2026-33026 CRITICAL nginx-ui Backup Restore Allows Tampering with Encrypted Backups
GHSA-qcjq-7f7v-pvc8 CVE-2024-23828 HIGH Nginx-UI vulnerable to authenticated RCE through injecting into the application config via CRLF
GHSA-xvq9-4vpv-227m CVE-2024-23827 CRITICAL Nginx-UI vulnerable to arbitrary file write through the Import Certificate feature
GHSA-h374-mm57-879c CVE-2024-22196 HIGH Authenticated (user role) SQL injection in `OrderAndPaginate` (GHSL-2023-270)
GHSA-pxmr-q2x3-9x9m CVE-2024-22197 HIGH Authenticated (user role) remote command execution by modifying `nginx` settings (GHSL-2023-269)
GHSA-8r25-68wm-jw35 CVE-2024-22198 HIGH Authenticated (user role) arbitrary command execution by modifying `start_cmd` setting (GHSL-2023-268)
GHSA-wr32-99hh-6f35 CVE-2026-44015 HIGH Nginx-UI has Server-Side Request Forgery (SSRF) via Cluster Proxy Middleware that Allows Access to Internal Services
GHSA-h27v-ph7w-m9fp CVE-2026-42221 HIGH Nginx-UI: Unauthenticated First-Run Installer Allows Remote Initial Admin Claim
GHSA-78mf-482w-62qj CVE-2026-34403 HIGH Nginx-UI: Cross-Site WebSocket Hijacking (CSWSH) via missing origin validation on all WebSocket endpoints
GHSA-x234-x5vq-cc2v CVE-2026-33031 HIGH Nginx-UI: Disabled users retain full API access through previously issued bearer tokens
GHSA-h6c2-x2m2-mwhf CVE-2026-33032 CRITICAL nginx-ui's Unauthenticated MCP Endpoint Allows Remote Nginx Takeover
GHSA-cp8r-8jvw-v3qg CVE-2026-33029 MODERATE nginx-ui Vulnerable to DoS via Negative Integer Input in Logrotate Interval
GHSA-m468-xcm6-fxg4 CVE-2026-33028 HIGH nginx-ui has Race Condition that Leads to Persistent Data Corruption and Service Collapse
GHSA-m8p8-53vf-8357 CVE-2026-33027 MODERATE Nginx Configuration Directory Vulnerable to Recursive Deletion via Improper Path Validation
GHSA-g9w5-qffc-6762 CVE-2026-27944 CRITICAL Nginx-UI Vulnerable to Unauthenticated Backup Download with Encryption Key Disclosure

CVE-2026-84360 at a Glance

CVE Identifier CVE-2026-84360
GHSA Identifier GHSA-vc32-4gwf-77xp
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-288: Authentication Bypass Using an Alternate Path or Channel
Affected Product Nginx UI
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-84360

To remediate this vulnerability, upgrade all affected Nginx UI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/0xJacky/Nginx-UI fixed: 1.9.10-0.20260703131214-23d1934099b0
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/0xJacky/Nginx-UI

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-84360, inspect your project dependencies for Nginx UI:

inspect dependencies for github.com/0xJacky/Nginx-UI

Analyze the terminal output to locate any version of Nginx UI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.10-0.20260703131214-23d1934099b0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-288: Authentication Bypass Using an Alternate Path or Channel, where the product requires authentication, but the product has an alternate path or channel that does not require authentication. In Nginx UI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary An OTP-enabled authenticated user who cannot use the HTTP configuration mutation endpoints without a valid secure session can still mutate Nginx configuration through `/mcp` and `/mcp_message` using only ordinary authentication. ### Details The HTTP configuration mutation surface is explicitly grouped behind `middleware.RequireSecureSession()`. By contrast, the MCP endpoints are exposed with only `middleware.AuthRequired()`. The MCP server exposes configuration mutation tools including `nginx_config_add` and `nginx_config_modify`, so OTP-enabled users gain an alternate path around the intended step-up requirement. Relevant code paths: - [api/config/router.go](/home/kali/Desktop/bounty/nginx-ui/api/config/router.go:14) - [internal/middleware/secure_session.go](/home/kali/Desktop/bounty/nginx-ui/internal/middleware/secure_session.go:52) - [mcp/router.go](/home/kali/Desktop/bounty/nginx-ui/mcp/router.go:9) - [mcp/config/config_add.go](/home/kali/Desktop/bounty/nginx-ui/mcp/config/config_add.go:34) - [mcp/config/config_modify.go](/home/kali/Desktop/bounty/nginx-ui/mcp/config/config_modify.go:55) This is a security-control bypass rather than a missing feature. The product already established that OTP-enabled users should complete a secure session before high-impact configuration mutations are accepted on the HTTP path. ### PoC I verified this locally in an isolated environment with a temporary end-to-end harness that exercised the real `/mcp` and `/mcp_message` routes. What the executed test did: 1. Created a temporary config directory and configured Nginx control commands to harmless local values (`true`) to avoid touching the host. 2. Created a real OTP-enabled user in a temporary SQLite database. 3. Generated a real JWT for that OTP-enabled user. 4. Started a local test server exposing the real `/mcp` and `/mcp_message` routes. 5. Opened an authenticated SSE connection to `/mcp` with the JWT and no `X-Secure-Session-ID`. 6. Initialized the MCP session over `/mcp_message`. 7. Called the real `nginx_config_add` tool over `/mcp_message`. 8. Verified that the tool succeeded and created `mcp-bypass.conf` in the managed config directory without any secure-session step-up. Observed result from the actual local verification: - The MCP session initialized successfully without any `X-Secure-Session-ID`. - The config file was written through the MCP tool path using only JWT authentication. ### Impact OTP-enabled accounts lose the intended step-up protection for high-impact Nginx configuration changes when MCP is enabled. A user who should be blocked until re-authenticating can still create or modify configuration files and trigger reload behavior through MCP.

CVE-2026-84360 Affected Nginx UI Versions

1 component(s)
Fixed Versions:
1.9.10-0.20260703131214-23d1934099b0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/0xJacky/Nginx-UI
Go
< 1.9.10-0.20260703131214-23d1934099b0
1.9.10-0.20260703131214-23d1934099b0

References

Frequently Asked Questions

What is CVE-2026-84360?
CVE-2026-84360 is a security vulnerability in Nginx UI involving OTP secure-session step-up can be bypassed via MCP configuration tools under CWE-288: Authentication Bypass Using an Alternate Path or Channel.
Which Nginx UI versions are affected?
Affected versions include releases prior to 1.9.10-0.20260703131214-23d1934099b0 across affected packages: github.com/0xJacky/Nginx-UI.
What version fixes CVE-2026-84360?
Upgrading to 1.9.10-0.20260703131214-23d1934099b0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/0xJacky/Nginx-UI affected?
Yes, github.com/0xJacky/Nginx-UI is affected in releases prior to 1.9.10-0.20260703131214-23d1934099b0. Upgrade your dependency to 1.9.10-0.20260703131214-23d1934099b0 or later.
What is the CVSS score of CVE-2026-84360?
CVE-2026-84360 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-84360?
CVE-2026-84360 is classified under CWE-288: Authentication Bypass Using an Alternate Path or Channel (The product requires authentication, but the product has an alternate path or channel that does not require authentication.).
How can I check Go dependencies for CVE-2026-84360?
Run the dependency tree command: 'inspect dependencies for github.com/0xJacky/Nginx-UI'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vc32-4gwf-77xp",
  "modified" : "2026-10-15T20:14:10Z",
  "published" : "2026-10-15T20:14:10Z",
  "aliases" : [ "CVE-2026-84360" ],
  "summary" : "Nginx UI: OTP secure-session step-up can be bypassed via MCP configuration tools",
  "details" : "### Summary\nAn OTP-enabled authenticated user who cannot use the HTTP configuration mutation endpoints without a valid secure session can still mutate Nginx configuration through `/mcp` and `/mcp_message` using only ordinary authentication.\n\n### Details\nThe HTTP configuration mutation surface is explicitly grouped behind `middleware.RequireSecureSession()`. By contrast, the MCP endpoints are exposed with only `middleware.AuthRequired()`. The MCP server exposes configuration mutation tools including `nginx_config_add` and `nginx_config_modify`, so OTP-enabled users gain an alternate path around the intended step-up requirement.\n\nRelevant code paths:\n- [api/config/router.go](/home/kali/Desktop/bounty/nginx-ui/api/config/router.go:14)\n- [internal/middleware/secure_session.go](/home/kali/Desktop/bounty/nginx-ui/internal/middleware/secure_session.go:52)\n- [mcp/router.go](/home/kali/Desktop/bounty/nginx-ui/mcp/router.go:9)\n- [mcp/config/config_add.go](/home/kali/Desktop/bounty/nginx-ui/mcp/config/config_add.go:34)\n- [mcp/config/config_modify.go](/home/kali/Desktop/bounty/nginx-ui/mcp/config/config_modify.go:55)\n\nThis is a security-control bypass rather than a missing feature. The product already established that OTP-enabled users should complete a secure session before high-impact configuration mutations are accepted on the HTTP path.\n\n### PoC\nI verified this locally in an isolated environment with a temporary end-to-end harness that exercised the real `/mcp` and `/mcp_message` routes.\n\nWhat the executed test did:\n1. Created a temporary config directory and configured Nginx control commands to harmless local values (`true`) to avoid touching the host.\n2. Created a real OTP-enabled user in a temporary SQLite database.\n3. Generated a real JWT for that OTP-enabled user.\n4. Started a local test server exposing the real `/mcp` and `/mcp_message` routes.\n5. Opened an authenticated SSE connection to `/mcp` with the JWT and no `X-Secure-Session-ID`.\n6. Initialized the MCP session over `/mcp_message`.\n7. Called the real `nginx_config_add` tool over `/mcp_message`.\n8. Verified that the tool succeeded and created `mcp-bypass.conf` in the managed config directory without any secure-session step-up.\n\nObserved result from the actual local verification:\n- The MCP session initialized successfully without any `X-Secure-Session-ID`.\n- The config file was written through the MCP tool path using only JWT authentication.\n\n### Impact\nOTP-enabled accounts lose the intended step-up protection for high-impact Nginx configuration changes when MCP is enabled. A user who should be blocked until re-authenticating can still create or modify configuration files and trigger reload behavior through MCP.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/0xJacky/Nginx-UI"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.10-0.20260703131214-23d1934099b0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-vc32-4gwf-77xp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-84360"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/0xJacky/nginx-ui"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-288" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:14:10Z",
    "nvd_published_at" : "2026-10-12T21:17:22Z"
  }
}