Vulnerability · CVE-2026-84316
Nginx UI: nginx config directive denylist (ValidateConfigFile) is bypassable via same-line ";" separation → authenticated directive injection (RCE on the official image)
Published Oct 15, 2026 · Nginx UI: nginx config
Check if you run it
No confirmed exploitation is on record for CVE-2026-84316. EPSS is 0.40%. Act only if a listed version of Nginx UI: nginx config is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Nginx UI: nginx config).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.40%
- Remediation
- Not established
- Affected products
- golang github.com
config.ValidateConfigFile is the security control that blocks dangerous nginx directives (js_ , perl_ , load_module of njs/perl modules, user root). Its directive scanner is bypassable: it splits the config by newlines and inspects only the FIRST token of each line, but nginx separates directives with ;, not newlines. Putting a benign directive first and the blocked directive after a ; on the SAME line defeats every check. The include directive is also …
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- golang github.comversion unspecified
How to fix CVE-2026-84316
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-84316. EPSS is 0.40%. Act only if a listed version of Nginx UI: nginx config is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.40%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2026 · GitLab Advisory Database
Detected
config.ValidateConfigFile is the security control that blocks dangerous nginx directives (js_ , perl_ , load_module of njs/perl modules, user root). Its directive scanner is bypassable: it splits the config by newlines and inspects only the FIRST token of each line, but nginx separates directives with ;, not newlines. Putting a benign directive first and the blocked directive after a ; on the SAME
Sources
- CVE.orgVulnerability recordCVE-2026-84316
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-84316
30-day exploitation probability 0.4%
first.org - GitLab Advisory DatabasePackage advisoryCVE-2026-84316
config.ValidateConfigFile is the security control that blocks dangerous nginx directives (js_ , perl_ , load_module of njs/perl modules, user root). Its directive scanner is bypassable: it splits the config by newlines and inspects only the FIRST token of each line, but nginx separates directives with ;, not newlines. Putting a benign directive first and the blocked directive after a ; on the SAME
advisories.gitlab.com
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.