# Nginx Configuration Directory Vulnerable to Recursive Deletion via Improper Path Validation

Advisory record · `GHSA-m8p8-53vf-8357`

- **Identifiers:** `GHSA-m8p8-53vf-8357` · `CVE-2026-33027` · `GO-2026-4907`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-73](https://cwe.mitre.org/data/definitions/73.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 30 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Mar 2026, 16:33 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 `<=1.99`; no fixed version yet

## Machine-written summary

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

> Nginx-UI (github.com/0xJacky/Nginx-UI) versions up to 1.99 are affected, though the source reports v2.3.3 as the tested version. An authenticated user can send URL-encoded traversal sequences in a configuration path so that a recursive deletion removes the entire /etc/nginx directory, causing a denial of service. Upgrade to v2.3.4, which the source names as the patched release; the package listing itself gives no fixed version.

Written 1 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

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m8p8-53vf-8357)

## Sources

- [GitHub Advisory Database: GHSA-m8p8-53vf-8357](https://github.com/advisories/GHSA-m8p8-53vf-8357)
- [OSV: GHSA-m8p8-53vf-8357](https://osv.dev/vulnerability/GHSA-m8p8-53vf-8357)
- <https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-m8p8-53vf-8357>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33027>
- <https://github.com/0xJacky/nginx-ui>
- <https://github.com/0xJacky/nginx-ui/releases/tag/v2.3.4>

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-m8p8-53vf-8357>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m8p8-53vf-8357/>. Everything for agents: <https://agentprime.io/llms.txt>.
