Skip to content

← Public intelligence

Go package

github.com/0xJacky/nginx-ui

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.0GoPublished

    Nginx-UI is Vulnerable to Unauthenticated Remote Code Execution via Backup Restore

    CVE-2026-42238 · GHSA-4pvg-prr3-9cxr

    Affected
    • Go github.com/0xJacky/nginx-ui < 2.3.8
    Fixed in
    2.3.8· Vendor fix available
    Issue
    Product: nginx-ui Repository: 0xJacky/nginx-ui (branch: dev) Vulnerability Class: Authentication Bypass → Arbitrary File Write → OS Command Injection Affected Component: POST /api/restore --- 1. Vulnerability Summary nginx-ui exposes a backup restore endpoint (POST /api/restore) that is completely unauthenticated during the first 10 minutes after process startup on any fresh installation. An unauthenticated remote attacker can upload a crafted backup archive that overwrites the application's configuration file (app.ini) and SQLite database. Because the attacker controls the restored app.ini, they can inject an arbitrary OS command into the TestConfigCmd setting. After the application automatically restarts to apply the restored config, a single follow-up request triggers that command as the user running nginx-ui — typically root in Docker deployments. The 10-minute unauthenticated window resets on every process restart, making this exploitable not only on initial deployments but on…

    Recommended action: Upgrade to 2.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.5GoPublished

    Nginx-UI Settings API Exposes Protected Secrets

    CVE-2026-42223 · GHSA-q4w7-56hr-83rm

    Affected
    • Go github.com/0xJacky/nginx-ui <= 2.3.7
    Fixed in
    2.3.8· Vendor fix available
    Issue
    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. Details Vulnerable Code api/settings/settings.go:49-64 - GetSettings serializes all fields Go's json.Marshal serializes all exported fields with json: tags. The protected:"true" struct tag is a custom tag - it has no effect on JSON serialization. Protection is Write-Only api/settings/settings.go:126-135 - ProtectedFill only used during saves ProtectedFill prevents overwriting protected fields during SaveSettings, but GetSettings has no…

    Recommended action: Upgrade to 2.3.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →