NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The…
Historical advisory recorded 25 Oct 2026 06:17:28 UTC. Read the latest advisory.
nvd · CVE-2026-27571
PublishedNATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The WebSockets handling of NATS messages handles compressed messages via the WebSockets negotiated compression. Prior to versions 2.11.2 and 2.12.3, 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, present in versions 2.11.2 and 2.12.3, was to bounds the decompression to fail once the message was too large, instead of continuing on. The vulnerability only affects deployments which use WebSockets and which expose the network port to untrusted end-points.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-27571
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-409 · CWE-770
Original publisher date fields
published: 2026-02-24T17:29:03.393
lastModified: 2026-06-17T10:27:19.650
1 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:nats-server:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON