CVE-2026-84360 0xJacky CVE debrief

Who should care

Defenders responsible for Nginx UI systems, particularly those using OTP-enabled users, should assess exposure and apply the fix to prevent potential configuration changes. This includes reviewing authentication and authorization settings, monitoring for MCP changes, and ensuring RequireSecureSession is properly configured. Security teams and vulnerability management teams should prioritize verifying exposure and applying the fix to prevent potential

Why it matters

CVE-2026-84360 is a high-severity vulnerability in Nginx UI that allows for potential configuration changes and bypass of intended security controls. Defenders should prioritize verifying exposure and applying the fix.

• Potential configuration changes through MCP
• Bypass of intended step-up control for OTP-enabled users
• Possible reload behavior triggered by configuration modifications
• Verification of authentication and authorization settings for OTP-enabled users

Technical summary

The vulnerability exists in the HTTP configuration mutation routes of Nginx UI, which require RequireSecureSession. However, /mcp and /mcp_message only require ordinary authentication, exposing nginx_config_add and nginx_config_modify. An OTP-enabled user with a normal JWT but no valid X-Secure-Session-ID can bypass the intended step-up control. This issue allows for potential configuration changes and reload behavior through MCP. The fix in version 2.4.1 addresses this vulnerability by enforcing RequireSecureSession for all relevant routes.

Defensive priority

Defenders should prioritize verifying exposure and applying the fix, as this vulnerability allows for potential configuration changes.

Recommended defensive actions

• Verify if the system is using Nginx UI version 2.4.1 or later
• Ensure RequireSecureSession is properly configured for HTTP configuration mutation routes
• Monitor for potential configuration changes through MCP
• Review and update authentication and authorization settings for OTP-enabled users
• Perform an inventory of assets using Nginx UI to identify potential exposure
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, its impact, and the fix. However, additional information on potential exploitation and affected systems is limited. Defenders should verify exposure and review authentication and authorization settings for OTP-enabled users. Evidence from the CVE Program and NIST NVD detail page supports this assessment. The fix in version 2.4.1 is confirmed, but further review of system configurations and potential MCP changes is necessary.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.