CVE-2026-42238
Unauthenticated RCE via Nginx UI restore endpoint.
Is CVE-2026-42238 being exploited?
Not confirmed. CVE-2026-42238 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.76% probability of exploitation in the next 30 days.
How severe is CVE-2026-42238?
CVE-2026-42238 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42238?
Yes. A fix has been recorded for CVE-2026-42238. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42238 affect?
CVE-2026-42238 affects Nginx UI <2.3.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42238?
Upgrade to 2.3.8 or disable the restore endpoint
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated backup restore can overwrite config/DB and execute OS commands as nginx-ui (root in Docker).
Immediate action required
- affected< 2.3.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.