9.4

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-33026

CVE-2026-33026: nginx-ui Backup Restore Allows Tampering with Encrypted Backups

Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.4, the nginx-ui backup restore mechanism allows attackers to tamper with encrypted backup archives and inject malicious configuration during restoration. This issue has been patched in version 2.3.4.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-33026

CVE-2026-33026:

9.4

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

SSVC / BOD 26-04 ↗

Exploitation pocAutomatable YesTech Impact Total

Select your environment

→SSVCScheduled60 days

Runtime reachability resolves your actual outcome.Book a demo

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/0xJacky/Nginx-UI	go	< 1.9.10-0.20260315015203-f61bcec547c0	1.9.10-0.20260315015203-f61bcec547c0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in a flawed backup and restore mechanism within nginx-ui, specifically a circular trust model for integrity verification. The system would encrypt a backup and provide the encryption key to the client. The integrity of the backup was checked using a hash_info.txt file which was itself part of the backup and encrypted with the same client-side key.

An attacker could obtain the backup and the key, decrypt the contents, modify them (e.g., inject a malicious command into a configuration file), recalculate the SHA-256 hashes of the modified files, update the hash_info.txt file, and then re-encrypt the entire backup.

The core of the exploitation occurs during the restore process. The vulnerable function Restore.DoRestore in controller/restore.go would receive this tampered backup. While it would perform a hash check, it would not abort the process upon failure. Instead, it would only issue a warning and proceed with the restoration, applying the attacker's malicious configuration.

The patch addresses this by introducing a proper cryptographic signature for the backup manifest, created using a server-side key. The Backup.CreateBackup function in controller/backup.go was modified to generate this signature. Correspondingly, the Restore.DoRestore function was updated to require and verify this signature, aborting the restore process if the verification fails. This breaks the circular trust model and prevents the restoration of tampered backups.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.