Nginx UI: Unauthenticated signed-request body staging can exhaust temporary storage — GHSA-J3HG-9RP3-5HW9
GitHub · GitHub · GHSA-J3HG-9RP3-5HW9
ID
GHSA-J3HG-9RP3-5HW9
GHSA-J3HG-9RP3-5HW9
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
high
high
CVSS
7.5
7.5
Summary
## Summary In Nginx UI versions 2.5.0 through 2.5.x, the node-signature authentication path staged an attacker-controlled request body in a temporary file and synchronized it to disk before validating the body digest and cryptographic signature. An unauthenticated remote client that can reach the API can provide syntactically valid signature metadata and cause storage and I/O consumption before the request is…
Timeline
- Published by source
- 2026-10-09
Risk context
- Reported severity or threat level: high.
- Reported CVSS score: 7.5 out of 10.
- Review exposure for the affected product or family: go: github.com/0xJacky/Nginx-UI.
Product
go: github.com/0xJacky/Nginx-UI
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-J3HG-9RP3-5HW9
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-10-09
- Last source activity
- 2026-10-09
- Additional identifiers
- CVE-2026-107805
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.