Advisory

GHSA-qrvq-68c2-7grw

Also known as: BIT-nats-2026-27571, CVE-2026-27571, GO-2026-4533

Summary

nats-server websockets are vulnerable to pre-auth memory DoS

Details

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).

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-02-24 16:04 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/nats-io/nats-server/v2

Go · All systems

Affected

  • introduced 0, fixed 2.11.12 (semver)

Fixed versions

2.11.12

Fix

github.com/nats-io/nats-server/v2

Go · All systems

Affected

  • introduced 2.12.0-RC.1, fixed 2.12.3 (semver)

Fixed versions

2.12.3

Fix

github.com/nats-io/nats-server

Go · All systems

Affected

  • introduced 0, last affected 1.4.1 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences