Live › vulnerability › CVE-2026-107807
Go to dashboardNginx UI, a web interface for managing Nginx, accepts the node secret master credential in the node_secret URL query parameter for HTTP and WebSocket authentication. Anyone who obtains that secret from logs, browser history or Referer headers can bypass password, JWT, session and second-factor checks and gain persistent admin API access, including configuration and secret material.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/0xJacky/Nginx-UI | go | >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074433-a3999bd78a3b | 1.9.10-0.20260728074433-a3999bd78a3b |
1.9.10-0.20260728074433-a3999bd78a3bnode_secret= to see whether the secret has already appeared in URLs1.9.10-0.20260728074433-a3999bd78a3b or later (the description cites fixed version )2.5.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, Nginx UI accepts the Node.Secret master credential through the node_secret query parameter in HTTP and WebSocket authentication paths instead of requiring the X-Node-Secret header. The credential can consequently appear in access logs, proxy logs, browser history, Referer headers, configuration URLs, and deployment environment data. A party that obtains the secret can bypass normal password, JWT, session, and second-factor checks and obtain persistent administrative API access, including access to configuration and secret material. This issue is fixed in version 2.5.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-107807")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.