CVE-2026-84318

Published: Ott 12, 2026 Last Modified: Ott 12, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,8
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: high

Description

AI Translation Available

Nginx UI is a web user interface for the Nginx web server. From 2.0.0-rc.6 until 2.4.1, the MCP tool nginx_config_add writes nginx configuration files to disk and triggers an nginx reload without calling config.ValidateConfigFile. The identical flow in the REST API (POST /api/configs) does call that function and correctly rejects dangerous directives. An authenticated attacker can exploit this gap to write config files containing any blocked directive (perl, js_import, load_module, user root, etc.), bypassing nginx-ui's entire security layer. On a server with the nginx Perl, njs, or Lua module loaded, this is post-authentication Remote Code Execution. This issue is fixed in version 2.4.1.

693

Protection Mechanism Failure

Draft
Abstraction: Pillar Structure: Simple
Common Consequences
Security Scopes Affected:
Access Control
Potential Impacts:
Bypass Protection Mechanism
Applicable Platforms
Technologies: Not Technology-Specific, ICS/OT
View CWE Details
https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a…
https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d…
https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1
https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1
https://github.com/0xJacky/nginx-ui/security/advisories/GHS…
https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-9jww-cxg5-rj9m