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, an unauthenticated MQTT client could cause the server to retain large incomplete MQTT CONNECT packets before authentication completed, consuming server memory while the parser waited for the advertised MQTT packet length. This issue is fixed in versions 2.14.3 and 2.12.12.
CVE-2026-58210
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 50.1%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 13, 2026
Advisory Details (5)
Auto-updated Jul 8, 2026MQTT partial CONNECT packets can exhaust pre-auth memory · Advisory · nats-io/nats-server · GitHub
Affected: v2.14.3 and v2.12.12.
https://github.com/nats-io/nats-server/security/advisories/GHSA-r72h-j7qq-v6qgRelease v2.14.3
Patch available: nats-io/nats-server v2.14.3
https://github.com/nats-io/nats-server/releases/tag/v2.14.3Release v2.12.12
Patch available: nats-io/nats-server v2.12.12
https://github.com/nats-io/nats-server/releases/tag/v2.12.12commit e016e47bbf70 (nats-io/nats-server)
Fix landed in nats-io/nats-server commit e016e47bbf70 — awaiting tagged release
https://github.com/nats-io/nats-server/commit/e016e47bbf70304945f2ae9dc397e4862adefaf5commit bce9ef39469e (nats-io/nats-server)
Fix landed in nats-io/nats-server commit bce9ef39469e — awaiting tagged release
https://github.com/nats-io/nats-server/commit/bce9ef39469e610aeddb819194ceb7f7edfc0861Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× 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.
- 2026-07-14 19:13 UTCEG score recompute
- 2026-07-14 08:12 UTCEG score recompute
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 21:12 UTCEG score recompute
- 2026-07-13 10:13 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 23:15 UTCEG score recompute
- 2026-07-12 12:15 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:16 UTCEG score recompute
- 2026-07-11 14:17 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:13 UTCEG score recompute
- 2026-07-10 16:15 UTCEG score recompute
- 2026-07-10 05:13 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 18:13 UTCEG score recompute
- 2026-07-09 07:14 UTCEG score recompute
- 2026-07-08 20:16 UTCEG score recompute
- 2026-07-08 20:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-58210?
When was CVE-2026-58210 disclosed?
Is CVE-2026-58210 actively exploited?
What is the CVSS score of CVE-2026-58210?
How do I remediate CVE-2026-58210?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58210
Is Your Infrastructure Affected by CVE-2026-58210?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.