0xJacky Nginx UI up to 2.4.x Authentication node_secret information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, has been found in 0xJacky Nginx UI up to 2.4.x. This impacts an unknown function of the component Authentication. Performing a manipulation of the argument node_secret results in information disclosure. This vulnerability is identified as CVE-2026-107807. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in 0xJacky Nginx UI up to 2.4.x. It has been classified as problematic. This affects an unknown functionality of the component Authentication. The manipulation of the argument node_secret with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-107807 since 10/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 2.5.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-95882). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Web Server

Vendor

• 0xJacky

Name

• Nginx UI

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion