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.
CVE-2026-27571
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
February 24, 2026
Last Modified
June 17, 2026
Advisory Details (4)
Auto-updated Aug 4, 2026nats-server WebSockets pre-auth memory DoS · Advisory · nats-io/nats-server · GitHub
https://github.com/nats-io/nats-server/security/advisories/GHSA-qrvq-68c2-7grwRelease v2.12.3
Patch available: nats-io/nats-server v2.12.3
https://github.com/nats-io/nats-server/releases/tag/v2.12.3Release v2.11.12
Patch available: nats-io/nats-server v2.11.12
https://github.com/nats-io/nats-server/releases/tag/v2.11.12commit f77fb7c4535e (nats-io/nats-server)
Fix landed in nats-io/nats-server commit f77fb7c4535e — awaiting tagged release
https://github.com/nats-io/nats-server/commit/f77fb7c4535e6727cc1a2899cd8e6bbdd8ba2017Vendor Advisories for CVE-2026-27571(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1773650060 | 2026-03-31 | redhat |
| redhat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1773650767 | 2026-03-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 4 ecosystems)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/nats-io/nats-server | — | — | — |
| github.com/nats-io/nats-server/v2 | — | 2.12.3 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nats-server | 2.10.1-1 ... 2.9.19-1 (14 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nats-server | 2.10.27-1, 2.12.4-1, 2.12.6-1, 2.14.1-1, 2.14.3-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nats-server | 2.10.27-1 | 2.12.4-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 18:04 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
Show 49 moreShow fewer
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:24 UTCVendor advisory
- 2026-08-14 09:06 UTCEG score recompute
- 2026-08-14 09:06 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:06 UTCEG score recompute
- 2026-08-13 01:06 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 00:52 UTCEG score recompute
- 2026-08-12 00:52 UTCVendor advisory
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 06:36 UTCEG score recompute
- 2026-08-11 06:36 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:17 UTCVendor advisory
- 2026-08-09 21:42 UTCEG score recompute
- 2026-08-09 21:42 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:44 UTCEG score recompute
- 2026-08-09 08:44 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 09:48 UTCVendor advisory
- 2026-08-07 20:50 UTCEG score recompute
- 2026-08-07 20:50 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 03:04 UTCEG score recompute
- 2026-08-06 03:04 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 05:57 UTCEG score recompute
- 2026-08-04 05:57 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:40 UTCEG score recompute▲ 1.60
- 2026-08-02 19:40 UTCVendor advisory
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 12:55 UTCEG score recompute
- 2026-07-27 12:55 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-27571?
When was CVE-2026-27571 disclosed?
Is CVE-2026-27571 actively exploited?
What is the CVSS score of CVE-2026-27571?
How do I remediate CVE-2026-27571?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27571
Is Your Infrastructure Affected by CVE-2026-27571?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.