Summary
NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
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 and can bridge MQTT activity into NATS subjects across routes and leafnode connections.
Problem Description
An MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections.
This could corrupt the forwarded protocol stream and allow injection of unintended NATS protocol operations, potentially across cluster nodes or accounts where route or gateway connections are present.
Anonymous MQTT deployments are higher risk because no credentials are required to reach the affected parser. Authenticated deployments are still affected for clients allowed to create MQTT subscriptions.
Affected Versions
Versions v2.14.0, v2.12.8 and below are vulnerable. The issue is fixed in v2.14.1 and v2.12.9.
Workarounds
Disable anonymous MQTT access where it is not required. Deployments that need MQTT have no known complete workaround other than upgrading.
References
- GHSA advisory: https://github.com/nats-io/nats-server/security/advisories/GHSA-qrcv-3558-gj4f
- Credit: @thesecguy45
Impact
CVE-2026-58213 has a CVSS score of 7.1 (High). The vector is network-reachable, low 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.9, 2.14.1); 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.9 or later; github.com/nats-io/nats-server/v2 to 2.14.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-58213? CVE-2026-58213 is a high-severity security vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.9. It is fixed in 2.12.9, 2.14.1.
- How severe is CVE-2026-58213? CVE-2026-58213 has a CVSS score of 7.1 (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-58213? github.com/nats-io/nats-server/v2 (go) versions < 2.12.9 is affected.
- Is there a fix for CVE-2026-58213? Yes. CVE-2026-58213 is fixed in 2.12.9, 2.14.1. Upgrade to this version or later.
- Is CVE-2026-58213 exploitable, and should I be worried? Whether CVE-2026-58213 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-58213 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-58213?
- Upgrade
github.com/nats-io/nats-server/v2to 2.12.9 or later - Upgrade
github.com/nats-io/nats-server/v2to 2.14.1 or later
- Upgrade