# CVE-2026-42223: GO-2026-5565 - Nginx-UI Settings API Exposes Protected Secrets in github.com/0xJacky/nginx-ui

Source: https://junglewise.ai/threats/cve-2026-42223-nginx-ui-settings-api-exposes-protected-secrets  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-04  
License: CC BY 4.0 with a link back

CVE-2026-42223 · Severity: medium · CVSS 6.5 · Published 2026-05-04

Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.8, the GetSettings API handler (api/settings/settings.go:24-65) serializes all settings structs to JSON and returns them to authenticated users. Many sensitive fields are tagged with protected:"true" - however, this tag is only enforced during writes (via ProtectedFill in SaveSettings) and is completely ignored during reads. This exposes 40+ protected fields including JwtSecret (enabling auth token forgery), NodeSecret (enabling cluster node impersonation), OIDC ClientSecret (enabling OAuth account takeover), and the IP whitelist configuration. This issue has been patched in version 2.3.8.

Technologies: [github.com/0xJacky/Nginx-UI (Go)](https://junglewise.ai/threats/technologies/github-com-0xjacky-nginx-ui), [Nginxui Nginx Ui](https://junglewise.ai/threats/technologies/nginxui-nginx-ui). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Nginxui](https://junglewise.ai/threats/vendors/nginxui).

## Quick answers

**Is CVE-2026-42223 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-42223 being exploited in the wild.

**How severe is CVE-2026-42223?** Medium severity, with a CVSS score of 6.5, published 4 May 2026.

**Which products and versions are affected?** github.com/0xJacky/Nginx-UI (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.3.8.

**Is there a fix for CVE-2026-42223?** Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 2.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-42223?** Check whether you run github.com/0xJacky/Nginx-UI (Go) or Nginxui Nginx Ui at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/0xJacky/Nginx-UI (Go): upgrade to 2.3.8 or later

  ```sh
  go get github.com/0xJacky/Nginx-UI@v2.3.8
  ```


## Affected products

- github.com/0xJacky/Nginx-UI (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.3.8
- Nginxui Nginx Ui

## Identifiers

- CVE-2026-42223
- GHSA-q4w7-56hr-83rm
- GO-2026-5565

## Related threats

- [Nginx UI Casdoor SSO login CSRF via constant state parameter](https://junglewise.ai/threats/cve-2026-84312-nginx-ui-casdoor-sso-callback-uses-a-constant-state-parameter)
- [Nginx UI OTP secure-session step-up bypass via MCP](https://junglewise.ai/threats/cve-2026-84360-nginx-ui-otp-secure-session-step-up-can-be-bypassed-via-mcp)
- [Nginx UI short token cache bypass after account re-enable](https://junglewise.ai/threats/cve-2026-84321-nginx-ui-standalone-short-tokens-survive-administrative)
- [Nginx UI auto backup path traversal in storage boundary](https://junglewise.ai/threats/cve-2026-84320-nginx-ui-auto-backup-name-allows-path-traversal-outside-validated)
- [Nginx UI MCP configuration directive validation bypass](https://junglewise.ai/threats/cve-2026-84319-nginx-ui-mcp-configuration-tools-bypass-restricted-directive)