Summary
NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled
Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT and edge computing.
The NATS Server can accept client connections over WebSocket and can also support MQTT over WebSocket when MQTT is configured.
Problem Description
A WebSocket listener could route requests for the MQTT-over-WebSocket path into MQTT handling even when MQTT was not configured.
On affected deployments, an unauthenticated client with access to the WebSocket listener could reach uninitialized MQTT state and crash the server process.
This affects deployments that enable WebSocket while leaving MQTT disabled. Deployments where MQTT is intentionally configured initialize the MQTT state and are not affected in the same way.
Affected Versions
Versions v2.14.2, v2.12.11 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.12.
Workarounds
Deployments not using WebSocket are not affected. Deployments using both WebSockets and MQTT are not affected. No known workaround for deployments that need WebSocket without MQTT-over-WebSocket. Upgrade to a fixed release.
References
- GHSA advisory: https://github.com/nats-io/nats-server/security/advisories/GHSA-p957-7v2w-g93g
- Credit: Vasco Franco, Trail of Bits
Impact
CVE-2026-58208 has a CVSS score of 6.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.12.12, 2.14.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/nats-io/nats-server/v2 to 2.12.12 or later; github.com/nats-io/nats-server/v2 to 2.14.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-58208? CVE-2026-58208 is a medium-severity security vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.12. It is fixed in 2.12.12, 2.14.3.
- How severe is CVE-2026-58208? CVE-2026-58208 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/nats-io/nats-server/v2 are affected by CVE-2026-58208? github.com/nats-io/nats-server/v2 (go) versions < 2.12.12 is affected.
- Is there a fix for CVE-2026-58208? Yes. CVE-2026-58208 is fixed in 2.12.12, 2.14.3. Upgrade to this version or later.
- Is CVE-2026-58208 exploitable, and should I be worried? Whether CVE-2026-58208 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-58208 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-58208?
- Upgrade
github.com/nats-io/nats-server/v2to 2.12.12 or later - Upgrade
github.com/nats-io/nats-server/v2to 2.14.3 or later
- Upgrade