Linux Foundation NATS

The JWT library in NATS nats-server before 2.1.9 has Incorrect Access Control because of how expired credentials are handled.

NATS nats-server 2.2.0 through 2.7.4 allows directory traversal because of an unintended path to a management action from a management account.

NATS nats-server before 2.7.2 has Incorrect Access Control. Any authenticated user can obtain the privileges of the System account by misusing the "dynamically provisioned sandbox accounts" feature.

NATS Server: Route API Auth Bypass

NATS has MQTT plaintext password disclosure

NATS allows MQTT clients to bypass ACL checks

NATS Server: Remote crash via integer overflow in Connz pagination

Denial of Service (DoS)

The JWT library in NATS nats-server before 2.1.9 allows a denial of service (a nil dereference in Go code).

An integer overflow in NATS Server before 2.0.2 allows a remote attacker to crash the server by sending a crafted request. If authentication is enabled, then the remote attacker must have first authenticated.

NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.

NATS Server: MQTT partial CONNECT packets can exhaust pre-auth memory

NATS Server: Pre-auth server crash via double INFO in leafnode handshake

NATS Server panic via malicious compression on leafnode port

NATS has pre-auth server panic via leafnode handling

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

NATS: Pre-auth remote server crash via WebSocket frame length overflow in wsRead

NATS is vulnerable to pre-auth DoS through WebSockets client service

nats-server websockets are vulnerable to pre-auth memory DoS

NATS credentials are exposed in monitoring port via command-line argv

xkeys Seal encryption used fixed key for all encryption

NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection

NATS nats-server before 2.7.4 allows Directory Traversal (with write access) via an element in a ZIP archive for JetStream streams. nats-streaming-server before 0.24.3 is also affected.

NATS nats-server before 2.9.23 and 2.10.x before 2.10.2 has an authentication bypass. An implicit $G user in an authorization block can sometimes be used for unauthenticated access, even when the intention of the configuration was for each user to have an account. The earliest affected version is 2.2.0.

NATS Server: Subscribe Authz Bypass via Wildcard-Overlap

NATS Server: Queue Subscribe Authz Bypass

NATS Server: Incomplete fix for CVE-2026-33249: Leaf node connections bypass Nats-Trace-Dest permission check

NATS is vulnerable to MQTT hijacking via Client ID

NATS Server: Incomplete Stripping of Nats-Request-Info Header Allows Identity Spoofing

NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers

NATS Server: `no_auth_user` pre-CONNECT fast path bypasses user connection restrictions

NATS JetStream has an authorization bypass through its Management API

NATS Server: MQTT subscribe ACL bypass via $MQTT.deliver.pubrel prefix (incomplete fix for CVE-2026-33217)

NATS Server: MQTT retained and QoS replay bypass subscribe deny filters

NATS: Message tracing can be redirected to arbitrary subject

NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching