CVE-2026-58250

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% 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, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.12.8 and 2.11.17, an unauthenticated peer with network access to a leafnode listener with compression enabled could crash the server during the pre-authentication leafnode handshake by sending repeated leafnode INFO protocol messages before authentication and account setup completed. This issue is fixed in versions 2.12.8 and 2.11.17.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (5)

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

Pre-auth server crash via double INFO in leafnode handshake — incomplete fix for CVE-2026-29785 and CVE-2026-33218 · Advisory · nats-io/nats-server · GitHub

Affected: v2.12.8 and v2.11.17.

https://github.com/nats-io/nats-server/security/advisories/GHSA-3g5q-cfh2-cq67
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_release Patch Available

Release v2.11.17

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

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

commit fc5fe3917753 (nats-io/nats-server)

Fix landed in nats-io/nats-server commit fc5fe3917753 — awaiting tagged release

https://github.com/nats-io/nats-server/commit/fc5fe39177533e9dbdd651d2458285bfae1dde27
github_commit

commit 8dcb26eaea78 (nats-io/nats-server)

Fix landed in nats-io/nats-server commit 8dcb26eaea78 — awaiting tagged release

https://github.com/nats-io/nats-server/commit/8dcb26eaea78fdcbe96dbee5986d6019fd5cb94a

Vendor Advisories for CVE-2026-58250(1)

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

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-12.14.1-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 158 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58250?
CVE-2026-58250 is a high 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.12.8 and 2.11.17, an unauthenticated peer with network access to a leafnode listener with compression enabled could crash the server during the pre-authentication leafnode handshake by…
When was CVE-2026-58250 disclosed?
CVE-2026-58250 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-58250 actively exploited?
CVE-2026-58250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58250?
CVE-2026-58250 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58250, 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-58250

Explore →

Is Your Infrastructure Affected by CVE-2026-58250?

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

Start Free Scan →Browse All CVEs