NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-29785: NATS Server panic via malicious compression on leafnode port

highCVSS 3.1 7.5GHSA-52jh-2xxh-pwh6

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

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 entries