CVE-2026-107805: Nginx UI: Unauthenticated signed-request body staging can exhaust temporary storage
Nginx UI is a web user interface for the Nginx web server. From 2.5.0 until 2.6.0, the node-signature authentication path performs temporary file staging of an attacker-controlled request body and synchronizes it before validating the body digest and cryptographic signature. An unauthenticated remote client that can reach the API and provide syntactically valid signature metadata can consume temporary filesystem capacity, disk input and output, and request-processing resources before rejection. The issue affects availability and does not bypass authentication or provide confidentiality or integrity impact. This issue is fixed in version 2.6.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Nginx UIto a version that resolves this vulnerability.Fixed in 2.6.0
Event History
Frequently Asked Questions
Which deployments are exposed?
Nginx UI versions from 2.5.0 until 2.6.0 are affected. Exposure requires that an unauthenticated remote client can reach the API endpoint using the node-signature authentication path.
What does an attacker need to trigger the resource consumption?
The attacker does not need credentials, but must provide syntactically valid signature metadata. Request-body staging and synchronization occur before the body digest and cryptographic signature are validated.
Does successful exploitation expose or alter protected data?
No. The reported impact is availability only: temporary filesystem capacity, disk I/O, and request-processing resources can be consumed before the request is rejected; authentication is not bypassed.