Skip to main content
VulnerabilityPublished

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

Affects github.com/nats-io/nats-server/v2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-58254· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.12.8 when convenient.

Data as of 21 Nov 2026, 00:33 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.12.8, 2.14.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade github.com/nats-io/nats-server/v2 to 2.12.8; github.com/nats-io/nats-server/v2 to 2.14.3.

Affected software

ProductAffectedFixed in
Gogithub.com/nats-io/nats-server/v2Affected
  • <2.12.8
Fixed in
  • 2.12.8
Gogithub.com/nats-io/nats-server/v2Affected
  • >=2.14.0-RC.1 <2.14.3
Fixed in
  • 2.14.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade NATS Server to version 2.12.8 or 2.14.3 or later, where the issue is fixed. As a workaround, avoid granting publish permissions from less-trusted leaf nodes to subjects where trace-only behavior could affect delivery guarantees. No other workarounds are known.

Description

NATS Server versions prior to 2.12.8 and between 2.14.0-RC.1 and before 2.14.3 have a vulnerability where leafnode connections bypass the Nats-Trace-Dest permission check. This allows a leafnode operator to send trace events to unauthorized subjects, potentially affecting message delivery or storage through trace-only behavior. The issue is fixed in versions 2.12.8 and 2.14.3.

References

Community reviews

Loading reviews…