CVE-2026-34403: 0xJacky nginx-ui · Missing Origin Validation in WebSockets
Affects 0xJacky nginx-uiSource CVE Database V5
Public exploit available · CVSS 5.5 Medium : upgrade to 2.3.5 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade nginx-ui and 0xjacky/nginx-ui to 2.3.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| 0xJackynginx-ui | Affected
| Fixed in
|
GitHub0xjacky/nginx-uipkg:github/0xjacky/nginx-uiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade nginx-ui to version 2.3.5 or later, where the origin validation for WebSocket connections has been properly implemented. Until upgraded, users should be cautious about visiting untrusted webpages while logged into nginx-ui, as the vulnerability requires user interaction.
Description
CVE-2026-34403 is a medium severity vulnerability in 0xJacky's nginx-ui prior to version 2.3.5. The issue arises because all WebSocket endpoints use a gorilla/websocket Upgrader with CheckOrigin always returning true, which allows Cross-Site WebSocket Hijacking (CSWSH). Since authentication tokens are stored in browser cookies without HttpOnly or SameSite attributes, a malicious webpage can establish authenticated WebSocket connections if an administrator visits it. Version 2.3.5 addresses this vulnerability.