dbcve.org
Nginx UiWeb server / proxy · Nginxui

CVE-2026-33029

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 2.3.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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. Prior to version 2.3.4, an input validation vulnerability in the logrotate configuration allows an authenticated user to cause a complete Denial of Service (DoS). By submitting a negative integer for the rotation interval, the backend enters an infinite loop or an invalid state, rendering the web interface unresponsive. This issue has been patched in version 2.3.4.

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
How this class of weakness works · CWE-20

The application accepts input without confirming it is well-formed or within expected bounds, so malformed data can push the program into states its author never anticipated. Attackers probe these gaps to trigger crashes, bypass logic, or feed tainted values into more dangerous operations downstream. Remediating it well means validating and normalising every input at the boundary against a strict allow-list — not merely filtering known-bad values.

General guidance for the improper input validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 2.3.4 or later
Fixed in 2.3.4
Recommended fix High confidence

2.3.4

  1. 1. Backup your current Nginx UI configuration and data directory
  2. 2. Stop the Nginx UI service
  3. 3. If using Docker, pull the latest image and recreate the container: 'docker pull scratchnginx/nginx-ui:latest' then recreate with your existing configuration
  4. 4. If using a package manager (e.g., apt, yum), update the package list and upgrade: 'apt update && apt install nginx-ui' or 'yum update nginx-ui'
  5. 5. If installing from source, download version 2.3.4 from the official repository and reinstall following the installation guide
  6. 6. Verify the service starts successfully
  7. 7. Log in to the Nginx UI web interface and navigate to the logrotate configuration settings
  8. 8. Confirm the input validation now rejects negative integers for the rotation interval

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33029 — 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-33029 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