nats-server Leaf node connections bypass Nats-Trace-Dest permission check
Published 20 Nov 2026 · Updated 20 Nov 2026
Is your project on an affected github.com/nats-io/nats-server/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <2.12.8
- Fixed in
- 2.12.8
go get github.com/nats-io/nats-server/v2@v2.12.8- Affected
- >=2.14.0-RC.1 <2.14.3
- Fixed in
- 2.14.3
go get github.com/nats-io/nats-server/v2@v2.14.3Details
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 supports leafnode connections between servers and message tracing through NATS headers.
Problem Description
Message trace destination checks were applied to ordinary client connections but not consistently to messages arriving through leafnode connections.
A leafnode operator could cause trace events to be sent to subjects that would not otherwise be permitted and could use trace-only behavior to prevent normal delivery or storage of affected messages.
Trace events can include routing, subscription, account, service import and JetStream metadata. The payload of the original application message is not chosen through the trace event itself.
Affected Versions
Versions v2.14.2, v2.12.7 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.8.
Workarounds
Where possible, avoid granting publish paths from less-trusted leaf nodes into subjects for which trace-only behavior would affect delivery guarantees. No other known workarounds are available aside from upgrading to a fixed release.
References
- GHSA advisory: <https://github.com/nats-io/nats-server/security/advisories/GHSA-p3j5-5hrq-p75h>
- Credit: Koda Reef
Is GHSA-p3j5-5hrq-p75h in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/nats-io/nats-server/v2, and gives you the command that fixes it.
More advisories for github.com/nats-io/nats-server/v2
- MediumCVE-2026-58208NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled · 20 Nov 2026
- HighCVE-2026-58210NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets · 20 Nov 2026
- MediumCVE-2026-58209NATS Server MQTT retained messages and QoS replay bypass subscription deny rules · 20 Nov 2026
- MediumCVE-2026-58214NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata · 19 Nov 2026
- HighCVE-2026-58213NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection · 19 Nov 2026
- LowCVE-2026-29785NATS Server panic via malicious compression on leafnode port in github.com/nats-io/nats-server · 26 Mar 2026
References
- Linkgithub.com/nats-io/nats-server/security/advisories/GHSA-p3j5-5hrq-p75h
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-58254
- Linkgithub.com/nats-io/nats-server/commit/cbe845932980b71563efac5cfa4cc751c88936cd
- Packagegithub.com/nats-io/nats-server
- Linkgithub.com/nats-io/nats-server/releases/tag/v2.12.8
- Linkgithub.com/nats-io/nats-server/releases/tag/v2.14.3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.