Summary
nats-server Leaf node connections bypass Nats-Trace-Dest permission check
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
Impact
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2026-58254 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.12.8, 2.14.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/nats-io/nats-server/v2 to 2.12.8 or later; github.com/nats-io/nats-server/v2 to 2.14.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-58254? CVE-2026-58254 is a medium-severity incorrect authorization vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.8. It is fixed in 2.12.8, 2.14.3. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2026-58254? CVE-2026-58254 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/nats-io/nats-server/v2 are affected by CVE-2026-58254? github.com/nats-io/nats-server/v2 (go) versions < 2.12.8 is affected.
- Is there a fix for CVE-2026-58254? Yes. CVE-2026-58254 is fixed in 2.12.8, 2.14.3. Upgrade to this version or later.
- Is CVE-2026-58254 exploitable, and should I be worried? Whether CVE-2026-58254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-58254 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-58254?
- Upgrade
github.com/nats-io/nats-server/v2to 2.12.8 or later - Upgrade
github.com/nats-io/nats-server/v2to 2.14.3 or later
- Upgrade