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

CVE-2026-58254: nats-server Leaf node connections bypass Nats-Trace-Dest permission check

mediumCVSS 4.0 5.3 · 3.1 6.5GHSA-p3j5-5hrq-p75h

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.

Published Nov 20, 2026

Affected packages

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
< 2.12.8
Fixed in
2.12.8
Check
go list -m github.com/nats-io/nats-server/v2

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
>= 2.14.0-RC.1, < 2.14.3
Fixed in
2.14.3
Check
go list -m github.com/nats-io/nats-server/v2

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.

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:
  • Credit: Koda Reef

Credited to kodareef5.

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