Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-vc32-4gwf-77xp

HighCVSS 8.1 / 10
Published Oct 15, 2026·Last modified Oct 19, 2026
Affected Components(1)
Go logogithub.com/0xjacky/nginx-ui
< 1.9.10-0.20260703131214-23d1934099b0
Description

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:

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.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
8.1

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.

Threat Intelligence
7.4

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS
0.42%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard