# CVE-2026-107811: 0xJacky/nginx-ui /api/nodes Leaks Cluster Node Tokens and Allows Cross-Node Impersonation as initUser > Authenticated users can leak cluster node tokens via API, enabling impersonation of trusted nodes to access sensitive management operations. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2026 - **Updated:** 14 Oct 2026 - **Also known as:** GHSA-32gc-wf3m-78w9, GO-2026-6702 ## What is CVE-2026-107811? CVE-2026-107811 is a high-severity vulnerability in 0xJacky nginx-ui, published on 9 Oct 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. From 2.0.0 until 2.5.0, ordinary authenticated users can access /api/nodes and /api/nodes/:id, whose responses serialize the node token field. The same token is accepted as X-Node-Secret by AuthRequired and maps the request to initUser, allowing the user to impersonate a trusted node against a reachable cluster member. This cross-node authentication bypass can expose sensitive management operations, including configuration synchronization and service restart. This issue is fixed in version 2.5.0. Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-107811? 3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728091109-0ecbd106c37b | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728091109-0ecbd106c37b | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728091109-0ecbd106c37b | Products: Nginxui Nginx Ui. ## How do I fix CVE-2026-107811? Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728091109-0ecbd106c37b or later. ## Is CVE-2026-107811 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107811 exists. ## Other vulnerabilities in 0xJacky nginx-ui - [CVE-2026-33032](https://insights.sbomify.com/CVE-2026-33032/): Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover (critical 9.8) - [CVE-2026-27944](https://insights.sbomify.com/CVE-2026-27944/): Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure (critical 9.8) - [CVE-2024-23827](https://insights.sbomify.com/CVE-2024-23827/): Nginx-UI arbitrary file write through the Import Certificate feature (critical 9.8) - [CVE-2026-107806](https://insights.sbomify.com/CVE-2026-107806/): Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite (critical 9.4) - [CVE-2026-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107811 and fix it if it is affected. What it is: CVE-2026-107811 is a high-severity vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107811 exists. Affected packages and fixed versions: - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728091109-0ecbd106c37b - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728091109-0ecbd106c37b - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728091109-0ecbd106c37b Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107811/ (Markdown: https://insights.sbomify.com/CVE-2026-107811/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107811 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107811 - OSV: https://osv.dev/vulnerability/CVE-2026-107811 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107811/ Summaries are generated and may contain mistakes; the official description above is the record.