CVE-2026-58210 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption 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 partial CONNECT packets can exhaust pre-auth memory
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-58210.
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, 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/nats-io/nats-server/v2 | all versions | 2.12.12go get github.com/nats-io/nats-server/v2@v2.12.12 |
| 🐹Go | github.com/nats-io/nats-server/v2 | ≥ 2.14.0-RC.1&&< 2.14.3 | 2.14.3go get github.com/nats-io/nats-server/v2@v2.14.3 |
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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-58210 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
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-58210 in your dependencies?
Find it across Go, including transitive dependencies.