CVE-2026-42220 Nginx-UI: Authenticated settings disclosure exposes node.secret and enables trusted-node authentication abuse, backup exfiltration, and restore-based nginx-ui state rollback

Medium 6.5 Published Updated

Authenticated users can retrieve sensitive node secrets, enabling trusted-node authentication abuse and state rollback in Nginx UI.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-42220?

CVE-2026-42220 is a medium-severity vulnerability in 0xJacky nginx-ui, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.8, an authenticated user can call GET /api/settings and retrieve sensitive configuration values, including node.secret. The same node.secret is accepted by AuthRequired() through the X-Node-Secret header (or node_secret query parameter), causing the request to be treated as authenticated via the trusted-node path and associated with the init user. This issue has been patched in version 2.3.8.

Weakness: CWE-863, CWE-200

Which versions are affected by CVE-2026-42220?

3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product.

PackageAffectedFixed in
github.com/0xJacky/Nginx-UI GoAll versionsNone
github.com/0xJacky/Nginx-UI GoAll versions to 1.9.9None
github.com/0xJacky/Nginx-UI GoAll versions to 1.9.9None

Products include Nginxui Nginx Ui.

How do I fix CVE-2026-42220?

Upgrade to a fixed version.

Is CVE-2026-42220 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42220 exists.

Sources

Also known as GHSA-7jrr-xw9c-mj39, GO-2026-5227.

Is CVE-2026-42220 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free