CVE-2026-107807
Awaiting Analysis Awaiting Analysis - Queue

Remote Code Execution in Nginx UI

Publication date: 2026-10-09

Last updated on: 2026-10-09

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-09
Last Modified
2026-10-09
Generated
2026-10-09
AI Q&A
2026-10-09
EPSS Evaluated
N/A
NVD
CVE-2026-107807
EUVD
EUVD-2026-95882

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
0xJacky nginx-ui >= 2.0.0, < 2.5.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-312 The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
CWE-598 The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Nginx UI versions 2.0.0 to 2.5.0. It allows the master credential Node.Secret to be passed via a URL query parameter instead of requiring the proper X-Node-Secret header. This causes the secret to be exposed in logs, browser history, and other places where URLs are stored or logged.

Detection Guidance

Check HTTP access logs, reverse proxy logs, and application logs for the presence of the node_secret parameter in URLs. Search for patterns like ?node_secret= or node_secret= in logs, browser history, and configuration files such as app.ini or environment variables.

Impact Analysis

An attacker who obtains the exposed Node.Secret can bypass all authentication methods like passwords, JWT, sessions, and 2FA. This grants full administrative access to the nginx-ui API, allowing them to read configurations, modify settings, access secrets, and potentially execute code on the system.

Compliance Impact

This vulnerability could lead to severe compliance violations. Exposure of credentials in logs or other storage violates data protection principles in GDPR and HIPAA. It may result in unauthorized access to sensitive data, requiring breach notifications and potential fines under these regulations.

Mitigation Strategies

Upgrade nginx-ui to version 2.5.0 or later. Remove any node_secret query parameters from URLs and configuration files. Rotate the node secret immediately and ensure it is not exposed in logs or environment variables.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107807. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart