CVE-2026-58208

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%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.14.3 and 2.12.12, a WebSocket listener could route requests for the MQTT-over-WebSocket path into MQTT handling even when MQTT was not configured, allowing an unauthenticated client with access to the WebSocket listener to reach uninitialized MQTT state and crash the server process. This issue is fixed in versions 2.14.3 and 2.12.12.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100CISA SSVC

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%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_commit, github_release.
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.12

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

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

commit 837536b98b3a (nats-io/nats-server)

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

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

commit 73b3dd9a5ea0 (nats-io/nats-server)

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

https://github.com/nats-io/nats-server/commit/73b3dd9a5ea0fa7bf08b702338676355b29b5fb4
githubMentions a patch (unverified)

MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled · Advisory · nats-io/nats-server · GitHub

Affected: v2.14.3 and v2.12.12.

https://github.com/nats-io/nats-server/security/advisories/GHSA-p957-7v2w-g93g

Vendor Advisories for CVE-2026-58208(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 (15 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.27-1 ... 2.14.6-1 (6 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, 2.14.1-1
  • every version up to 2.14.3-1: fixed in 2.14.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 42× 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 215 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58208?
CVE-2026-58208 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.14.3 and 2.12.12, a WebSocket listener could route requests for the MQTT-over-WebSocket path into MQTT handling even when MQTT was not configured, allowing an unauthenticated client with…
When was CVE-2026-58208 disclosed?
CVE-2026-58208 was first published on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58208 actively exploited?
CVE-2026-58208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58208?
CVE-2026-58208 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58208?
A fix for CVE-2026-58208 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58208 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-58208

Explore →

Is Your Infrastructure Affected by CVE-2026-58208?

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