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%, top 54% 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
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.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.5(medium)
EG Risk
34(Track)
EG Risk 34/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

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
github Patch Available

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 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 23× in last 7d / 106× 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 150 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 53.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58208, 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-58208

Explore →

Is Your Infrastructure Affected by CVE-2026-58208?

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

Start Free Scan →Browse All CVEs