CVE-2026-58211

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

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 client could be registered as the configured no_auth_user through a parser path used when the first client operation was not CONNECT, bypassing user-level connection restrictions such as allowed_connection_types or proxy_required that normal authentication would apply. This issue is fixed in versions 2.14.3 and 2.12.12.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (1)

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

`no_auth_user` pre-CONNECT fast path bypasses user connection restrictions · Advisory · nats-io/nats-server · GitHub

Affected: v2.14.3 and v2.12.12.

https://github.com/nats-io/nats-server/security/advisories/GHSA-hmmp-q8cx-v964

Vendor Advisories for CVE-2026-58211(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnats-server2-12-main-2.12.12-1.hum12026-07-06redhat
redhatnats-server2-14-main-2.14.3-1.hum12026-07-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 15× in last 7d / 53× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58211?
CVE-2026-58211 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 could be registered as the configured noauthuser through a parser path used when the first client operation was not CONNECT, bypassing user-level connection…
When was CVE-2026-58211 disclosed?
CVE-2026-58211 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-58211 actively exploited?
CVE-2026-58211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.7% of all scored CVEs.
What is the CVSS score of CVE-2026-58211?
CVE-2026-58211 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-58211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58211, 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-58211

Explore →

Is Your Infrastructure Affected by CVE-2026-58211?

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

Start Free Scan →Browse All CVEs