CVE-2026-27571: nats-server websockets are vulnerable to pre-auth memory DoS
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 telegraf 1.31.0-12 on Azure Linux 3.0 1.31.0-13; cbl2 telegraf 1.29.4-18 on CBL Mariner 2.0 1.29.4-19.
Low priority for now. Upgrade to azl3 telegraf 1.31.0-12 on Azure Linux 3.0 1.31.0-13; cbl2 telegraf 1.29.4-18 on CBL Mariner 2.0 1.29.4-19 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
NATS-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.
- Published
- Feb 24, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-409
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | nats-server | cpe:2.3:a:linuxfoundation:nats-server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
nats-io nats-server
- < 2.11.12, >= 2.12.0-RC.1, < 2.12.3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linuxfoundation nats-serverbefore 2.11.12
- linuxfoundation nats-server2.12.0 and later · before 2.12.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | nats-server | from 0 | — |
| Debian:14 | nats-server | before 2.12.4-1 | 2.12.4-1 |
| Go | github.com/nats-io/nats-server | from 0 | — |
| Go | github.com/nats-io/nats-server | up to and including 1.4.1 | — |
| Go | github.com/nats-io/nats-server/v2 | from 2.12.0-RC.1 · before 2.12.3 | 2.12.3 |
| Go | github.com/nats-io/nats-server/v2 | before 2.11.12 | 2.11.12 |
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-26892The JWT library in NATS nats-server before 2.1.9 has Incorrect Access Control because of how expired credentials are handled.40Plan
- CVE-2022-28357NATS nats-server 2.2.0 through 2.7.4 allows directory traversal because of an unintended path to a management action from a management…39Monitor
- CVE-2026-58253NATS Server: Route API Auth Bypass35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-28466Mar 7, 2021 · Denial of Service (DoS)31Monitor
- ← EarlierCVE-2023-47090Oct 30, 2023 · NATS nats-server before 2.9.23 and 2.10.x before 2.10.2 has an authentication bypass.26Monitor
- Later →CVE-2026-33215Mar 24, 2026 · NATS is vulnerable to MQTT hijacking via Client ID26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 telegraf 1.31.0-12 on Azure Linux 3.0 | 1.31.0-13 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 telegraf 1.29.4-18 on CBL Mariner 2.0 | 1.29.4-19 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:nats-server | 2.12.4-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/nats-io/nats-server/v2 | 2.11.12 | Package registry (OSV) |
| Go:github.com/nats-io/nats-server/v2 | 2.12.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.