CVE-2026-29785GO-2026-4829BIT-NATS-2026-29785GHSA-52JH-2XXH-PWH6
NATS Server panic via malicious compression on leafnode port
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.11.14, 2.12.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.14 and 2.12.5, 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). Versions 2.11.14 and 2.12.5 contain a fix. As a workaround, disable compression on the leafnode port.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- nats-io nats-server
fixed in 2.11.14; From 2.12.0-RC.1 · fixed in 2.12.5
- github.com/nats-io/nats-serverGo
All versions
- github.com/nats-io/nats-server/v2Go
fixed in 2.11.14; From 2.12.0-RC.1 · fixed in 2.12.5
- github.com/nats-io/nats-server/v2Go
fixed in 2.11.14
- github.com/nats-io/nats-server/v2Go
From 2.12.0-RC.1 · fixed in 2.12.5