CVE-2026-58213 is a high-severity (CVSS 7.1) CWE-74 vulnerability in github.com/nats-io/nats-server/v2. A fix is available for github.com/nats-io/nats-server/v2 — see the affected versions and patch details below.
NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-58213.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/nats-io/nats-server/v2🐹github.com/nats-io/nats-server/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/nats-io/nats-server/v2 | all versions | 2.12.9go get github.com/nats-io/nats-server/v2@v2.12.9 |
| 🐹Go | github.com/nats-io/nats-server/v2 | ≥ 2.14.0-RC.1&&< 2.14.1 | 2.14.1go get github.com/nats-io/nats-server/v2@v2.14.1 |
Affected Products
nats-serverlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nats-io/nats-server/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/nats-io/nats-server/v2 to 2.12.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-58213 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | nats-server2-14-main-2.14.3-1.hum1 | RHSA-2026:36016 |
| Red Hat Hardened Images | nats-server2-12-main-2.12.12-1.hum1 | RHSA-2026:36017 |
Frequently Asked Questions
Is CVE-2026-58213 in your dependencies?
Find it across Go, including transitive dependencies.