All vulnerabilities

Servers and applications

GHSA-qq4p-5m6w-ww57

Node Secret Leaked in nginx Access Logs via Query String Authentication

Severity
Critical 9.6
Published
12 Aug 2026
Last changed
12 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
2.5.0
Weakness
CWE-598
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read data · Change data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Sources
Project advisories (GitHub)

Description

isTrustedNodeRequest() in internal/middleware/websocket_origin.go accepts the cluster node secret via the URL query string parameter node_secret. Because nginx-ui is the application that manages nginx — and nginx logs all requests including query strings to its access log by default — the secret is written in plaintext to a log file that nginx-ui itself exposes via its own log-reading API endpoints. Any authenticated user with log-read access can retrieve the node secret and use it to bypass all WebSocket authentication.

The vulnerable code in isTrustedNodeRequest():

func isTrustedNodeRequest(r *http.Request) bool { secret := strings.TrimSpace(r.Header.Get("X-Node-Secret")) if secret == "" { secret = strings.TrimSpace(r.URL.Query().Get("node_secret")) // ← written to nginx logs } return secret != "" && secret == settings.NodeSettings.Secret }

When a child node connects to the master via WebSocket, it may authenticate using a URL such as:

From 0xJacky/nginx-ui's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Nginx UIServers and applications · github:0xjacky/nginx-ui
  • From 2.0.0 before 2.5.0

About Nginx UI

Yet another WebUI for Nginx

From its GitHub repository.
Docker Hub pulls
1,512,532Docker Hub, 15 Nov 2026
GitHub stars
11,783GitHub, 15 Nov 2026
Forks
921GitHub, 15 Nov 2026
Latest release
v3.0.3GitHub, 15 Nov 2026
Released
12 Nov 2026GitHub
License
AGPL-3.0GitHub
First published on GitHub
19 Feb 2021GitHub

References