CVE-2026-29785: NATS Server panic via malicious compression on leafnode port
Background NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing. When configured to accept leafnode connections (for a hub/spoke topology of multiple nats-servers), then the default configuration allows for negotiating compression; a malicious remote NATS server can trigger a server panic via that compression.
Published Mar 24, 2026 · Updated Mar 27, 2026
Affected packages
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- < 2.11.14
- Fixed in
- 2.11.14
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- >= 2.12.0-RC.1, < 2.12.5
- Fixed in
- 2.12.5
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server
- Ecosystem
- Go
- Affected
- > 0
- Fixed in
- No patched version yet
- Check
go list -m github.com/nats-io/nats-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.
When configured to accept leafnode connections (for a hub/spoke topology of multiple nats-servers), then the default configuration allows for negotiating compression; a malicious remote NATS server can trigger a server panic via that compression.
Problem Description
If the nats-server has the "leafnode" configuration enabled (not default), then anyone who can connect can crash the nats-server by triggering a panic. This happens pre-authentication and requires that compression be enabled (which it is, by default, when leafnodes are used).
Context: a NATS server can form various clustering topologies, including local clusters, and superclusters of clusters, but leafnodes allow for separate administrative domains to link together with limited data communication; eg, a server in a moving vehicle might use a local leafnode for agents to connect to, and sync up to a central service as and when available. The leafnode configuration here is where the central server allows other NATS servers to connect into it, almost like regular NATS clients. Documentation examples typically use port 7422 for leafnode communications.
Affected Versions
Version 2, prior to v2.11.14 or v2.12.5
Workarounds
Disable compression on the leafnode port:
leafnodes {
port: 7422
compression: off
}References
- https://github.com/nats-io/nats-server/security/advisories/GHSA-52jh-2xxh-pwh6
- https://github.com/nats-io/nats-server/commit/a1488de6f2ba6e666aef0f9cce0016f7f167d6a8
- https://advisories.nats.io/CVE/secnote-2026-04.txt
- https://nvd.nist.gov/vuln/detail/CVE-2026-29785
- https://github.com/advisories/GHSA-52jh-2xxh-pwh6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-58208
NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled
medium6.8Nov 20, 2026CVE-2026-58209
NATS Server MQTT retained messages and QoS replay bypass subscription deny rules
medium4.3Nov 20, 2026CVE-2026-58210
NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets
high7.5Nov 20, 2026CVE-2026-58254
nats-server Leaf node connections bypass Nats-Trace-Dest permission check
medium6.5Nov 20, 2026CVE-2026-58213
NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
high7.1Nov 19, 2026CVE-2026-58214
NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata
medium4.3Nov 19, 2026
