CVE-2026-34403
Nginxui Nginx Ui ≤ 2.3.5
Raw vector
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:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-34403 is a medium-severity Missing Origin Validation in WebSockets (CWE-1385) vulnerability in Nginxui Nginx Ui. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-34403 is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability, tracked under CWE-1385, affecting Nginx UI, a web user interface for the Nginx web server. In versions prior to 2.3.5, all WebSocket endpoints utilize a gorilla/websocket Upgrader where the CheckOrigin function unconditionally returns true, bypassing origin validation. This issue is exacerbated by authentication tokens stored in browser cookies set via JavaScript, lacking HttpOnly or explicit SameSite attributes, enabling cross-site access to these tokens. The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).
An attacker can exploit this vulnerability by luring a logged-in administrator to visit an attacker-controlled webpage. The malicious page can then establish authenticated WebSocket connections to the nginx-ui instance, leveraging the victim's cookies for authentication. This allows the attacker to perform actions on behalf of the administrator over the hijacked WebSocket, potentially compromising confidentiality and integrity of the nginx-ui configuration and related Nginx server management.
The GitHub security advisory (GHSA-78mf-482w-62qj) and release notes for version 2.3.5 detail the patch, which addresses the CheckOrigin misconfiguration and cookie handling deficiencies. Security practitioners should upgrade to nginx-ui version 2.3.5 or later to mitigate the issue, and review WebSocket implementations for similar origin validation flaws.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23972
Vulnerability Data
Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.5, all WebSocket endpoints in nginx-ui use a gorilla/websocket Upgrader with CheckOrigin unconditionally returning true, allowing Cross-Site WebSocket Hijacking (CSWSH). Combined with the fact that…
more
authentication tokens are stored in browser cookies (set via JavaScript without HttpOnly or explicit SameSite attributes), a malicious webpage can establish authenticated WebSocket connections to the nginx-ui instance when a logged-in administrator visits the attacker-controlled page. Version 2.3.5 patches the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.4.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on logical access, which can include origin checks before accepting WebSocket connections.
Enforces information flow policies that can require validation of communication origins at system boundaries.
Protects authenticity of communications sessions, which origin validation helps ensure for WebSocket handshakes.
Monitors and controls communications at external interfaces, directly supporting origin validation for inbound WebSocket traffic.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require origin validation for WebSocket endpoints.
Origin validation is a required step when authenticating WebSocket connection requests.
Enforcing authorization policy on incoming connections can require origin checks.
Network-level controls that block unauthorized logical access can mitigate missing origin checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing origin validation in WebSocket implementations.
Network security controls can enforce origin validation and restrict WebSocket connections to trusted sources.
Secure configuration of network services can include origin checks for WebSocket endpoints.
Application security requirements can mandate origin validation for WebSocket communications.
Secure architecture principles can require proper origin validation mechanisms in WebSocket implementations.
Secure coding standards can explicitly require origin validation for WebSocket connections.