NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-27571: nats-server websockets are vulnerable to pre-auth memory DoS

mediumCVSS 3.1 5.9GHSA-qrvq-68c2-7grw

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

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 entries