Summary
NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets
Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT and edge computing.
The NATS Server supports MQTT clients, including authentication and parsing of MQTT CONNECT packets.
Problem Description
An unauthenticated MQTT client could cause the server to retain large incomplete MQTT CONNECT packets before authentication completed.
The parser retained partial pre-authentication packet data while waiting for the advertised MQTT packet length to be completed. An attacker could therefore consume server memory until authentication timeouts closed the connections.
Affected Versions
Versions v2.14.2, v2.12.11 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.12.
Workarounds
Deployments not using MQTT are not affected. Deployments that need MQTT should upgrade to a fixed release.
References
- GHSA advisory: https://github.com/nats-io/nats-server/security/advisories/GHSA-r72h-j7qq-v6qg
- Credit: Asritha Bodepudi, Trail of Bits
Impact
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2026-58210 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.12.12, 2.14.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/nats-io/nats-server/v2 to 2.12.12 or later; github.com/nats-io/nats-server/v2 to 2.14.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-58210? CVE-2026-58210 is a high-severity uncontrolled resource consumption vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.12. It is fixed in 2.12.12, 2.14.3. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2026-58210? CVE-2026-58210 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/nats-io/nats-server/v2 are affected by CVE-2026-58210? github.com/nats-io/nats-server/v2 (go) versions < 2.12.12 is affected.
- Is there a fix for CVE-2026-58210? Yes. CVE-2026-58210 is fixed in 2.12.12, 2.14.3. Upgrade to this version or later.
- Is CVE-2026-58210 exploitable, and should I be worried? Whether CVE-2026-58210 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-58210 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-58210?
- Upgrade
github.com/nats-io/nats-server/v2to 2.12.12 or later - Upgrade
github.com/nats-io/nats-server/v2to 2.14.3 or later
- Upgrade