dbcve.org
Nginx UiWeb server / proxy · Nginxui

CVE-2026-44015

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to after 2.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nginx UI is a web user interface for the Nginx web server. In 2.3.4 and earlier, 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Nginx UI versions 2.3.4 and earlier contain an authenticated SSRF vulnerability in the Proxy middleware. Attackers with valid user credentials can create a cluster node configuration pointing to an arbitrary internal URL (such as localhost or internal network addresses) and then trigger forwarding of API requests by specifying the X-Node-ID header, effectively bypassing network segmentation controls.

MitigationUpgrade to a version newer than 2.3.4. If no patched version is available, implement strict network access controls, disable the cluster node functionality for untrusted users, and monitor for suspicious X-Node-ID header usage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx UiWeb server / proxy
Affected:<= 2.3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Nginx UI version
    Check the Docker container image tag or running container version using 'docker ps' and 'docker images | grep nginx-ui', or check any package manager installation records
    Affected if The version is 2.3.4 or earlier
  2. Verify if proxy/cluster node functionality is accessible
    Log into the Nginx UI administrative interface and navigate to the Proxy or Cluster Node configuration section. If these menu items exist and are accessible to your user account, the feature is enabled
    Affected if The Proxy or Cluster Node configuration interface is accessible to your user account
  3. Inspect existing cluster node configurations
    Within Nginx UI, review any existing cluster node configurations for entries pointing to internal addresses (127.0.0.1, localhost, 192.168.x.x, 10.x.x.x, or other RFC 1918 private network ranges)
    Affected if Any cluster node is configured to point to internal/local network addresses that should not be externally accessible
  4. Review access logs for X-Node-ID headers
    Examine Nginx UI access logs for incoming requests containing the 'X-Node-ID' header. Check both Nginx UI logs and any reverse proxy logs in front of it
    Affected if Requests with X-Node-ID headers are present in logs, especially pointing to internal services or localhost
  5. Confirm user authentication is properly configured
    Verify that Nginx UI requires authentication and that user accounts are not using default or weak credentials. Check the authentication settings in the configuration panel
    Affected if Anonymous access is permitted or shared/default credentials are in use

A user is affected if they are running Nginx UI version 2.3.4 or earlier with the cluster node/proxy feature accessible to authenticated users who can configure nodes pointing to internal network addresses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.4
Interim mitigation

Upgrade to a version newer than 2.3.4. If no patched version is available, implement strict network access controls, disable the cluster node functionality for untrusted users, and monitor for suspicious X-Node-ID header usage.

Recommended fix Moderate confidence

Nginx UI version 2.3.5 or later

  1. 1. Backup your current Nginx UI configuration and data
  2. 2. Upgrade Nginx UI to version 2.3.5 or later which contains the fix for this SSRF vulnerability
  3. 3. Verify the upgrade was successful by checking the version number
  4. 4. Review and test the cluster node functionality to ensure legitimate features still work
Caveat Review release notes for any changes to cluster node functionality; minimal risk expected as this is a security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Ui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44015 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data