NVD / CVE Program· CNA GitHub_M

CVE-2026-33032: Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover

Noroxi assessment

Priority: Plan (action score 50/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 35.2% (FIRST EPSS); higher than 98.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260402T184258-150000.1.158.1.

Add it to your regular patch cycle. Upgrade to govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260402T184258-150000.1.158.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Published: Mar 30, 2026
Updated: Jun 17, 2026
EPSS: 35.2% · 98th percentile
CWE: CWE-306

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 11 / 30 · 35.2%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
nginxui	nginx ui	cpe:2.3:a:nginxui:nginx_ui

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

nginxui nginx uiup to 2.3.5 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

0xJacky nginx-ui
- <= 2.3.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/0xJacky/Nginx-UI	from 0	—
Go	github.com/0xJacky/Nginx-UI	up to and including 1.99	—
openSUSE:Leap 15.6	govulncheck-vulndb	before 0.0.20260402T184258-150000.1.158.1	0.0.20260402T184258-150000.1.158.1

Same product

nginxui: all records

Other highest-scoring records for the same primary product.

CVE-2026-27944Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure
46Plan
CVE-2024-49368Unchecked logrotate settings lead to arbitrary command execution
43Plan
CVE-2026-44015Nginx UI: Server-Side Request Forgery (SSRF) via Cluster Proxy Middleware Allows Access to Internal Services
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-33029Mar 30, 2026 · Nginx UI: DoS via Negative Integer Input in Logrotate Interval
27Monitor
← EarlierCVE-2026-33030Mar 30, 2026 · Nginx UI: Unencrypted Storage of DNS API Tokens and ACME Private Keys
39Monitor
Later →CVE-2026-33026Mar 30, 2026 · nginx-ui Backup Restore Allows Tampering with Encrypted Backups
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
opensuse:govulncheck-vulndb	0.0.20260402T184258-150000.1.158.1 · openSUSE:Leap 15.6	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1
Proof-of-concept repository on GitHub ×4

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2026-33032	—
Proof-of-concept repository on GitHub	stars:3	2026-04-03
Proof-of-concept repository on GitHub	stars:1	2026-04-17
Proof-of-concept repository on GitHub	stars:5	2026-04-18
Proof-of-concept repository on GitHub	stars:0	2026-08-21

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMar 30, 2026
First PoCApr 3, 2026+3 d
TodayNov 5, 2026+220 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-2794425 days apartNginx UI: Unauthenticated Backup Download with Encryption Key Disclosure
46Plan
CVE-2026-4222135 days apartnginx-ui: Unauthenticated First-Run Installer Allows Remote Initial Admin Claim
39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-330300 days apartNginx UI: Unencrypted Storage of DNS API Tokens and ACME Private Keys
39Monitor
CVE-2026-4401543 days apartNginx UI: Server-Side Request Forgery (SSRF) via Cluster Proxy Middleware Allows Access to Internal Services
39Monitor
CVE-2026-330280 days apartNginx UI: Race Condition Leads to Persistent Data Corruption and Service Collapse
28Monitor
CVE-2026-330270 days apartNginx UI: Improper Path Validation Allows Recursive Deletion of the Nginx Configuration Directory
27Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-306 · Missing Authentication for Critical Function

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

The bug in code

The whole CWE-306 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1// Added for the support team
2app.post("/maintenance/reset", resetDevice);

Fixed

1if (config.maintenanceEnabled) {
2  app.post(
3    "/maintenance/reset",
4    requireSession, requireRole("admin"), resetDevice
5  );
6}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

websec.net/blog/cve-2026-33032-unauthenticated-nginx-ui-mcp-takeover-69e1200f9fceb1f3fbe9c47f

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: GitHub_M

CVE.org (CNA)Apr 16, 2026, 9:42 PM UTC
CISA ADPApr 16, 2026, 9:42 PM UTC
NVDJun 17, 2026, 6:36 AM UTC
FIRST EPSSNov 4, 2026, 12:00 AM UTC
OSV / GHSANov 5, 2026, 3:18 AM UTC
NucleiNov 5, 2026, 3:17 AM UTC
PoC-in-GitHubNov 5, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.