CVE-2026-27571: nats-server websockets are vulnerable to pre-auth memory DoS
Impact The WebSockets handling of NATS messages handles compressed messages via the WebSockets negotiated compression. The implementation bound the memory size of a NATS message but did not independently bound the memory consumption of the memory stream when constructing a NATS message which might then fail validation for size reasons.
Published Feb 24, 2026 · Updated Feb 27, 2026
Affected packages
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- < 2.11.12
- Fixed in
- 2.11.12
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- >= 2.12.0-RC.1, < 2.12.3
- Fixed in
- 2.12.3
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server
- Ecosystem
- Go
- Affected
- <= 1.4.1
- Fixed in
- No patched version yet
- Check
go list -m github.com/nats-io/nats-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The WebSockets handling of NATS messages handles compressed messages via the WebSockets negotiated compression. The implementation bound the memory size of a NATS message but did not independently bound the memory consumption of the memory stream when constructing a NATS message which might then fail validation for size reasons.
An attacker can use a compression bomb to cause excessive memory consumption, often resulting in the operating system terminating the server process.
The use of compression is negotiated before authentication, so this does not require valid NATS credentials to exploit.
The fix was to bounds the decompression to fail once the message was too large, instead of continuing on.
Patches
This was released in nats-server without being highlighted as a security issue. It should have been, this was an oversight. Per the NATS security policy, because this does not require a valid user, it is CVE-worthy.
This was fixed in the v2.11 series with v2.11.12 and in the v2.12 series with v2.12.3.
Workarounds
This only affects deployments which use WebSockets and which expose the network port to untrusted end-points.
References
This was reported to the NATS maintainers by Pavel Kohout of Aisle Research (www.aisle.com).
References
- https://github.com/nats-io/nats-server/security/advisories/GHSA-qrvq-68c2-7grw
- https://github.com/nats-io/nats-server/commit/f77fb7c4535e6727cc1a2899cd8e6bbdd8ba2017
- https://github.com/nats-io/nats-server/releases/tag/v2.11.12
- https://github.com/nats-io/nats-server/releases/tag/v2.12.3
- https://nvd.nist.gov/vuln/detail/CVE-2026-27571
- https://pkg.go.dev/vuln/GO-2026-4533
- https://github.com/advisories/GHSA-qrvq-68c2-7grw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-58208
NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled
medium6.8Nov 20, 2026CVE-2026-58209
NATS Server MQTT retained messages and QoS replay bypass subscription deny rules
medium4.3Nov 20, 2026CVE-2026-58210
NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets
high7.5Nov 20, 2026CVE-2026-58254
nats-server Leaf node connections bypass Nats-Trace-Dest permission check
medium6.5Nov 20, 2026CVE-2026-58213
NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
high7.1Nov 19, 2026CVE-2026-58214
NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata
medium4.3Nov 19, 2026
