CVE-2026-84316 json
Nginx UI: nginx config directive denylist (ValidateConfigFile) is bypassable via same-line ";" separation → authenticated directive injection (RCE on the official image)
published 30d ago modified 23d ago also EUVD-2026-97906 , GHSA-cf23-7qxj-xmhr , GO-2026-6782
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, config.ValidateConfigDirectives splits configuration by newline and checks only the first directive token on each line even though Nginx permits multiple semicolon-separated directives on one line. An authenticated caller can place a benign directive first and a restricted load_module, js_import, perl, or user root directive later on the same line, or can use an unrestricted include directive to load restricted content. These mechanisms bypass validation on REST, nginx_config_modify, site, and stream write paths; when an executable module is available, the injected configuration can execute code in the Nginx worker context. This issue is fixed in version 2.4.1.
Patch / fix
- go github.com/0xJacky/Nginx-UI 1.9.10-0.20260703131214-23d1934099b0
- nginxui nginx_ui 2.4.1
Is CVE-2026-84316 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 29d ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-cf23-7qxj-xmhr referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/0xJacky/Nginx-UI | <1.9.10-0.20260703131214-23d1934099b0 |
1.9.10-0.20260703131214-23d1934099b0 |
Affected products
- 0xJacky nginx-ui
Classification
References
-
github.com
/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2
web
-
github.com
/0xJacky/nginx-ui/security/advisories/GHSA-cf23-7qxj-xmhr
exploit, web, advisory
-
github.com
/0xJacky/nginx-ui/releases/tag/v2.4.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-84316
advisory
-
github.com
/0xJacky/nginx-ui
package
Sources
- CVE List CVE-2026-84316
- GitHub Advisory GHSA-cf23-7qxj-xmhr
- NVD CVE-2026-84316
- OSV GO-2026-6782
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.