Advisory record · GHSA-5r62-gj48-897x

Nginx UI: MCP configuration tools bypass restricted directive validation and allow secondary authenticated users to execute NJS in Nginx worker context

CVSS 8.3 HighEPSS 0.0028 · 20th percentile

Published by the GitHub Advisory Database at 15 Oct 2026, 20:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/0xJacky/Nginx-UIGo<1.9.10-0.20260703131214-23d1934099b01.9.10-0.20260703131214-23d1934099b0
Identifiers
GHSA-5r62-gj48-897x · CVE-2026-84319 · GO-2026-6774
Weakness (CWE)
CWE-693
Published
15 Oct 2026
Updated
19 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nginx UI versions before 1.9.10-0.20260703131214-23d1934099b0 have a flaw where the MCP configuration tools (the /mcp and /mcp_message endpoints, including nginx_config_add) skip the restricted directive validation that the HTTP configuration API applies. A secondary authenticated user with MCP enabled can therefore load NJS modules, import attacker-supplied JavaScript, and run it in the Nginx worker context, which can alter responses, routing, headers, and redirects. Upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later. The source gives no workaround beyond the fix.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.