---
id: "CVE-2026-107807"
kind: "vulnerability"
aliases: ["CVE-2026-107807", "GHSA-pvgv-gcp7-v38g", "GO-2026-6708"]
title: "Nginx UI: Node Secret Credential Exposure via URL Query Parameter in github.com/0xJacky/Nginx-UI"
severity: "high"
cvss: 8.8
epss: 0.00296
exploited: false
status: "open"
category: "package"
products: [{"name": "github.com/0xJacky/Nginx-UI", "fixed": ["1.9.10-0.20260728074433-a3999bd78a3b"], "affected": ">= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074433-a3999bd78a3b", "ecosystem": "go"}]
ecosystems: ["go"]
tags: ["go", "nginx", "nginx-ui", "package", "self-hosted"]
not_affected_if: ["default-config"]
published_at: "2026-10-09T16:17:25+00:00"
first_seen_at: "2026-10-23T19:13:08+00:00"
updated_at: "2026-10-23T19:52:38+00:00"
sources: [{"source": "govuln", "url": "https://pkg.go.dev/vuln/GO-2026-6708", "first_seen_at": "2026-10-23T19:13:08+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-107807", "first_seen_at": "2026-10-23T19:13:43+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107807", "first_seen_at": "2026-10-23T19:35:23+00:00"}]
---

# Nginx UI: Node Secret Credential Exposure via URL Query Parameter in github.com/0xJacky/Nginx-UI

Nginx 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, check and fix written by a model from the sources; labelled as such._

## Affected

- go:github.com/0xJacky/Nginx-UI affected >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074433-a3999bd78a3b fixed 1.9.10-0.20260728074433-a3999bd78a3b

## How to check

Check the Go module version of github.com/0xJacky/Nginx-UI in go.mod and confirm it is at or above 1.9.10-0.20260728074433-a3999bd78a3b.
Search proxy and access logs for 'node_secret=' to see whether the secret has already appeared in URLs.

## Fix

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074433-a3999bd78a3b or later (the description cites fixed version 2.5.0).
Rotate the Node.Secret after upgrading, since it may already be exposed in logs.

## Timeline

- 2026-10-23T19:13:08+00:00 govuln https://pkg.go.dev/vuln/GO-2026-6708
- 2026-10-23T19:13:43+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-107807
- 2026-10-23T19:35:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-107807

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_