nats-server Leaf node connections bypass Nats-Trace-Dest permission checkGHSA-p3j5-5hrq-p75h
MEDIUMFix: nats-io/nats-server@cbe8459GHSA-p3j5-5hrq-p75h is a medium-severity (CVSS 6.5) CWE-863 vulnerability in github.com/nats-io/nats-server/v2. A fix is available for github.com/nats-io/nats-server/v2 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p3j5-5hrq-p75h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/nats-io/nats-server/v2🐹github.com/nats-io/nats-server/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/nats-io/nats-server/v2 | all versions | 2.12.8go get github.com/nats-io/nats-server/v2@v2.12.8 |
| 🐹Go | github.com/nats-io/nats-server/v2 | ≥ 2.14.0-RC.1&&< 2.14.3 | 2.14.3go get github.com/nats-io/nats-server/v2@v2.14.3 |
Affected Products
nats-serverlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nats-io/nats-server/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/nats-io/nats-server/v2 to 2.12.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p3j5-5hrq-p75h is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | nats-server2-14-main-2.14.3-1.hum1 | RHSA-2026:36016 |
| Red Hat Hardened Images | nats-server2-12-main-2.12.12-1.hum1 | RHSA-2026:36017 |
Frequently Asked Questions
Is GHSA-p3j5-5hrq-p75h in your dependencies?
Find it across Go, including transitive dependencies.