CVE-2026-84319 0xJacky CVE debrief

Who should care

Defenders responsible for Nginx UI installations, especially those with secondary authenticated users, should assess exposure and prioritize updates to version 2.4.1 or later. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and ensure updates are applied to prevent potential code execution.

Why it matters

CVE-2026-84319 is a high-severity vulnerability in Nginx UI that allows secondary authenticated users to execute NJS in the Nginx worker context. Defenders should prioritize verifying exposure and updating vulnerable installations to prevent potential code execution.

• Secondary authenticated users can execute NJS in the Nginx worker context.
• Loading ngx_http_js_module.so and importing attacker-controlled JavaScript is possible.
• The vulnerability allows for potential code execution in the Nginx worker context.
• Verification of exposure and updating to version 2.4.1 or later is necessary.

Technical summary

The vulnerability in Nginx UI allows secondary authenticated users to bypass restricted directive validation and execute NJS in the Nginx worker context. This is achieved by writing and applying restricted configuration content through the MCP configuration interface. The issue allows loading ngx_http_js_module.so, importing attacker-controlled JavaScript, and executing NJS. The vulnerability is fixed in version 2.4.1, and defenders should prioritize verifying exposure and updating vulnerable installations to prevent potential code execution.

Defensive priority

Defenders should prioritize verifying exposure of Nginx UI installations, especially those with secondary authenticated users, and ensure they are updated to version 2.4.1 or later.

Recommended defensive actions

• Verify Nginx UI installations for exposure, especially those with secondary authenticated users.
• Update vulnerable Nginx UI installations to version 2.4.1 or later.
• Monitor Nginx UI logs for suspicious activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability, its impact, and the fix. However, there is limited information on the affected scope, exploitation, and victim impact. Defenders should verify Nginx UI installations, especially those with secondary authenticated users, and ensure they are updated to version 2.4.1 or later. Evidence is limited, and further verification is necessary to assess exposure.

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.