CVE-2026-42238 affects Nginx UI prior to version 2.3.8. On fresh installations, the application exposes the backup restore endpoint for a limited startup window without authentication. During the first 10 minutes after process startup, a remote attacker can submit a crafted backup archive to the restore functionality and overwrite the application's configuration and SQLite database. By controlling the restored configuration, the attacker can place an arbitrary operating system command into the TestConfigCmd setting. When the application restarts to apply the restored configuration, a subsequent request can trigger execution of that command in the security context of the nginx-ui process. In common Docker deployments, that process may run as root, making the issue a pre-authentication remote command execution vulnerability chained from an improper authentication condition on a sensitive administrative endpoint.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.