NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.3 and 2.12.8, message trace destination checks were applied to ordinary client connections but not consistently to messages arriving through leafnode connections, allowing a leafnode operator to send trace events to subjects that would not otherwise be permitted and to use trace-only behavior to prevent normal delivery or storage of affected messages. This issue is fixed in versions 2.14.3 and 2.12.8.
CVE-2026-58254
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 22.7%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 13, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026Incomplete fix for CVE-2026-33249: Leaf node connections bypass Nats-Trace-Dest permission check · Advisory · nats-io/nats-server · GitHub
Affected: v2.14.3 and v2.12.8.
https://github.com/nats-io/nats-server/security/advisories/GHSA-p3j5-5hrq-p75hRelease v2.14.3
Patch available: nats-io/nats-server v2.14.3
https://github.com/nats-io/nats-server/releases/tag/v2.14.3Release v2.12.8
Patch available: nats-io/nats-server v2.12.8
https://github.com/nats-io/nats-server/releases/tag/v2.12.8commit cbe845932980 (nats-io/nats-server)
Fix landed in nats-io/nats-server commit cbe845932980 — awaiting tagged release
https://github.com/nats-io/nats-server/commit/cbe845932980b71563efac5cfa4cc751c88936cdWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 06:15 UTCEG score recompute▲ 1.20
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 16:08 UTCNVD updateCVSS v3 → 6.5
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:15 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 02:15 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:16 UTCEG score recompute
- 2026-07-09 22:15 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 20:16 UTCEG score recompute
- 2026-07-08 20:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-58254?
When was CVE-2026-58254 disclosed?
Is CVE-2026-58254 actively exploited?
What is the CVSS score of CVE-2026-58254?
How do I remediate CVE-2026-58254?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58254
Is Your Infrastructure Affected by CVE-2026-58254?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.