CVE-2026-58207

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% 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: 1%CVSS: 6.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 client able to send account-scoped connection monitoring requests could crash the server by supplying Connz pagination Offset and Limit values that overflowed internal arithmetic before the response window was safely bounded. This issue is fixed in versions 2.14.3 and 2.12.12.

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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
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 894d94119276 (nats-io/nats-server)

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

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

commit 2ae047139e37 (nats-io/nats-server)

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

https://github.com/nats-io/nats-server/commit/2ae047139e37a38cb01e259a67909e7a39fa38e9
github Patch Available

Remote crash via integer overflow in Connz pagination · Advisory · nats-io/nats-server · GitHub

Affected: v2.14.3 and v2.12.12.

https://github.com/nats-io/nats-server/security/advisories/GHSA-q59r-vq66-pxc2

Vendor Advisories for CVE-2026-58207(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 8× in last 7d / 43× 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 154 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58207?
CVE-2026-58207 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.12, a client able to send account-scoped connection monitoring requests could crash the server by supplying Connz pagination Offset and Limit values that overflowed internal…
When was CVE-2026-58207 disclosed?
CVE-2026-58207 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-58207 actively exploited?
CVE-2026-58207 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 54.6% of all scored CVEs.
What is the CVSS score of CVE-2026-58207?
CVE-2026-58207 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-58207?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58207, 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-58207

Explore →

Is Your Infrastructure Affected by CVE-2026-58207?

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

Start Free Scan →Browse All CVEs