CVE-2026-58250

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-42380 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

October 25, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
nats-server2.10.1-1 ... 2.9.19-1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.27-1 ... 2.15.1-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-1
  • every version up to 2.14.1-1: fixed in 2.14.1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 262 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-58250?
CVE-2026-58250 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-58250 published?
The CVE record for CVE-2026-58250 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-58250 actively exploited?
CVE-2026-58250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58250?
CVE-2026-58250 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58250?
A fix for CVE-2026-58250 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58250 are linked in the Vendor Advisories panel on this page.

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.