# Nginx-UI: Unauthenticated first-boot instance claim via POST /api/install allows remote bootstrap takeover

Advisory record · `GHSA-mxqh-q9h6-v8pq`

- **Identifiers:** `GHSA-mxqh-q9h6-v8pq` · `CVE-2026-42222` · `GO-2026-5521`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 6 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 May 2026, 16:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/0xJacky/nginx-ui` (Go): affected `=2.3.5`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Nginx-UI version 2.3.5 is affected, and no fixed version is listed. On a fresh instance still in its first-run state, the bootstrap endpoint POST /api/install accepts requests without authentication during the initial 10-minute setup window. A remote attacker who reaches the instance in that window can set the administrator credentials and application secrets, gaining full administrative control. The source gives few details on fixes; the only mitigation it describes is to keep fresh installs from being reachable by untrusted parties until setup is complete.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mxqh-q9h6-v8pq)

## Sources

- [GitHub Advisory Database: GHSA-mxqh-q9h6-v8pq](https://github.com/advisories/GHSA-mxqh-q9h6-v8pq)
- [OSV: GHSA-mxqh-q9h6-v8pq](https://osv.dev/vulnerability/GHSA-mxqh-q9h6-v8pq)
- <https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-mxqh-q9h6-v8pq>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-42222>
- <https://github.com/0xJacky/nginx-ui>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mxqh-q9h6-v8pq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mxqh-q9h6-v8pq/>. Everything for agents: <https://agentprime.io/llms.txt>.
