CVE-2026-58254

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Incomplete 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-p75h
github_release Patch Available

Release v2.14.3

Patch available: nats-io/nats-server v2.14.3

https://github.com/nats-io/nats-server/releases/tag/v2.14.3
github_release Patch Available

Release v2.12.8

Patch available: nats-io/nats-server v2.12.8

https://github.com/nats-io/nats-server/releases/tag/v2.12.8
github_commit

commit 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/cbe845932980b71563efac5cfa4cc751c88936cd

Vendor Advisories for CVE-2026-58254(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnats-server2-14-main-2.14.3-1.hum12026-07-06redhat
redhatnats-server2-12-main-2.12.12-1.hum12026-07-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.1-1 ... 2.9.19-1 (14 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-1, 2.14.1-1, 2.14.3-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-1, 2.14.1-12.14.3-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 52× 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.

  1. 2026-08-30 07:29 UTCEG score recompute
  2. 2026-08-30 07:29 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 21:49 UTCEG score recompute
  6. 2026-08-27 21:49 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 08:21 UTCEG score recompute
  10. 2026-08-26 08:21 UTCVendor advisory
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 23:38 UTCEG score recompute
  13. 2026-08-24 23:38 UTCVendor advisory
  14. 2026-08-23 21:37 UTCEG score recompute
  15. 2026-08-23 21:37 UTCVendor advisory
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-22 19:38 UTCEG score recompute
  18. 2026-08-22 19:38 UTCVendor advisory
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 17:37 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 15:37 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 10:49 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 69 more
  1. 2026-08-17 08:46 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 06:47 UTCEG score recompute
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 04:48 UTCEG score recompute
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 02:47 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 00:47 UTCEG score recompute
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-11 22:48 UTCEG score recompute
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-09 18:48 UTCEG score recompute
  14. 2026-08-09 13:46 UTCEPSS rescore
  15. 2026-08-08 16:49 UTCEG score recompute
  16. 2026-08-07 14:49 UTCEG score recompute
  17. 2026-08-06 13:47 UTCEPSS rescore
  18. 2026-08-06 12:49 UTCEG score recompute
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-05 10:50 UTCEG score recompute
  21. 2026-08-04 15:10 UTCEPSS rescore
  22. 2026-08-04 10:39 UTCEPSS rescore
  23. 2026-08-04 08:22 UTCEG score recompute
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 03:51 UTCEG score recompute
  26. 2026-08-02 02:27 UTCEPSS rescore
  27. 2026-08-01 04:16 UTCEPSS rescore
  28. 2026-07-30 23:18 UTCEG score recompute
  29. 2026-07-30 16:28 UTCEPSS rescore
  30. 2026-07-30 01:30 UTCEPSS rescore
  31. 2026-07-30 01:30 UTCEPSS rescore
  32. 2026-07-28 17:39 UTCEG score recompute
  33. 2026-07-28 15:37 UTCEPSS rescore
  34. 2026-07-27 15:38 UTCEG score recompute
  35. 2026-07-27 14:14 UTCEPSS rescore
  36. 2026-07-26 14:54 UTCEPSS rescore
  37. 2026-07-26 14:54 UTCEPSS rescore
  38. 2026-07-26 12:26 UTCEG score recompute
  39. 2026-07-25 14:18 UTCEPSS rescore
  40. 2026-07-25 14:18 UTCEPSS rescore
  41. 2026-07-24 14:18 UTCEPSS rescore
  42. 2026-07-24 14:18 UTCEPSS rescore
  43. 2026-07-23 14:18 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 03:20 UTCEG score recompute
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-21 15:25 UTCEPSS rescore
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-19 02:29 UTCEPSS rescore
  52. 2026-07-18 10:04 UTCEPSS rescore
  53. 2026-07-16 17:03 UTCEPSS rescore
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 02:00 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-14 06:15 UTCEG score recompute 1.20
  59. 2026-07-13 22:31 UTCEPSS rescore
  60. 2026-07-13 16:08 UTCNVD updateCVSS v3 → 6.5
  61. 2026-07-13 06:13 UTCEPSS rescore
  62. 2026-07-13 06:13 UTCEPSS rescore
  63. 2026-07-12 05:46 UTCEPSS rescore
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-09 19:10 UTCEPSS rescore
  68. 2026-07-08 20:16 UTCEG score recompute
  69. 2026-07-08 20:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58254?
CVE-2026-58254 is a medium vulnerability published on July 8, 2026. 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…
When was CVE-2026-58254 disclosed?
CVE-2026-58254 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58254 actively exploited?
CVE-2026-58254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-58254?
CVE-2026-58254 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-58254?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58254, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58254

Explore →

Is Your Infrastructure Affected by CVE-2026-58254?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.