SSRF (Server-Side Request Forgery) in github.com/0xJacky/Nginx-UI (CVE-2026-44015)
Summary
SSRF in github.com/0xJacky/Nginx-UI (CVE-2026-44015). Confidential information can be exposed externally. Exploitable via GET /api/settings.
Original description
The description as published by the source.
Summary
An authenticated user can perform Server-Side Request Forgery (SSRF) by creating a cluster node pointing to an arbitrary internal URL and then sending API requests with the X-Node-ID header. The Proxy middleware forwards these requests to the attacker-specified internal address, bypassing network segmentation and enabling access to services bound to localhost or internal networks.
Details
The nginx-ui Proxy middleware (internal/middleware/proxy.go) intercepts API requests containing an X-Node-ID header and forwards them to the URL of the corresponding cluster node. An attacker can:
- Read the
node_secretfromGET /api/settings(accessible to any authenticated user) - Create a cluster node via
POST /api/nodespointing to any internal URL:
{
"name": "ssrf_node",
"url": "http://127.0.0.1:51820",
"token": "",
"enabled": true
}
- Send any API request with the
X-Node-IDheader set to the created node's ID:
GET /api/settings HTTP/1.1
Authorization:
X-Node-ID: 1
- The Proxy middleware forwards this request to
http://127.0.0.1:51820/api/settings, making a server-side request to the internal address.
Vulnerable code path:
internal/middleware/proxy.go—Proxy(): no validation of the node URL; allows127.0.0.1,localhost, internal IPs, cloud metadata endpoints, etc.
The node URL is not restricted to external addresses or validated against an allowlist. Combined with the njs Code Injection vulnera…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44015 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like GET /api/settings over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-44015" on the vendor's site.
CVE-2026-44015 (github.com/0xJacky/Nginx-UI) — CWE-918 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/settings / POST /api/nodes / node_secret / localhost
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via GET /api/settings.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: GET /api/settings / POST /api/nodes / node_secret / localhost.
Severity: High (CVSS 8.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/settings requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/0xJacky/Nginx-UI' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/0xJacky/Nginx-UI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/0xJacky/Nginx-UIを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com