CVE-2026-33032
CVE-2026-33032 is a critical-severity vulnerability in 0xJacky nginx-ui (CVSS 3.1 base score 9.8), classified as CWE-306 (Missing Authentication for Critical Function). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as proof of concept. As of 2026-11-22, EPSS estimates a 35.9% probability of exploitation in the next 30 days, in the 98th percentile of scored CVEs.
Updated
- CVSS 3.1
- 9.8 CRITICAL
- EPSS
- 35.9% (98th pct)
- CISA KEV
- Not listed
- Published
- 2026-03-30
- Weakness
- CWE-306
Description
Nginx UI is a web user interface for the Nginx web server. In versions 2.3.5 and prior, the nginx-ui MCP (Model Context Protocol) integration exposes two HTTP endpoints: /mcp and /mcp_message. While /mcp requires both IP whitelisting and authentication (AuthRequired() middleware), the /mcp_message endpoint only applies IP whitelisting - and the default IP whitelist is empty, which the middleware treats as "allow all". This means any network attacker can invoke all MCP tools without authentication, including restarting nginx, creating/modifying/deleting nginx configuration files, and triggering automatic config reloads - achieving complete nginx service takeover. At time of publication, there are no publicly available patches.
Key Findings
as of 2026-11-22- Its current EPSS score (35.9%) is higher than that of 43% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 3 days and forensic triage on other assets.
Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable yes, technical impact total, 2026-03-30).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| 0xJacky | 0xJacky nginx-ui | <= 2.3.5 |
References
2 linksRecord Details
- Published
- 2026-03-30
- Last updated
- 2026-04-16
- Assigner (CNA)
- GitHub_M
- Credited to
- -
More from 0xJacky
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.