CVE-2026-58208: NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled

Medium CVSS 6.8

OSV id
GHSA-p957-7v2w-g93g
Also known as
CVE-2026-58208
Published
Last modified

Affected packages

PackageAffected versionsFixed in
github.com/nats-io/nats-server/v2
Go
< 2.12.12 2.12.12
github.com/nats-io/nats-server/v2
Go
>= 2.14.0-RC.1, < 2.14.3 2.14.3

How to fix it

github.com/nats-io/nats-server/v2 (Go)

Upgrade github.com/nats-io/nats-server/v2 to 2.12.12 or later.

go get github.com/nats-io/nats-server/v2@v2.12.12
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

github.com/nats-io/nats-server/v2 (Go)

Upgrade github.com/nats-io/nats-server/v2 to 2.14.3 or later.

go get github.com/nats-io/nats-server/v2@v2.14.3
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.