CVE-2026-33219: NATS is vulnerable to pre-auth DoS through WebSockets client service
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, a malicious client which can connect to the WebSockets port can cause unbounded memory use in the nats-server before authentication; this requires sending a corresponding amount of data. This is a milder variant of CVE-2026-27571. That earlier issue was a compression bomb, this vulnerability is not. Attacks against this new issue thus require significant client bandwidth. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, disable websockets if not required for project deployment.
Security readout for executives and security teams
Plain-English summary
NATS servers with WebSockets enabled can be made to consume excessive memory before login on affected versions. The main business risk is service disruption, not data theft. The vendor-fixed versions are 2.11.15 and 2.12.6, and disabling WebSockets is the stated workaround when unused.
Executive priority
Prioritize remediation for internet-facing or partner-facing NATS WebSockets deployments. Internal-only systems are lower urgency but should still be upgraded during the next maintenance window.
Technical view
CVE-2026-33219 is a pre-authentication denial-of-service issue in nats-server WebSockets handling. A client reaching the WebSockets port can drive unbounded memory use by sending sufficient data. Sources describe it as CWE-770 and a milder, non-compression-bomb variant of CVE-2026-27571.
Likely exposure
Exposure is most likely where nats-server runs before 2.11.15, or 2.12.0-RC.1 through before 2.12.6, with the WebSockets port reachable by untrusted networks.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Exploitation requires network access to the WebSockets listener and significant client bandwidth, reducing practicality but not removing availability risk.
Researcher notes
Do not treat this as the earlier compression-bomb issue. The stated condition is unbounded memory consumption before authentication through WebSockets, requiring proportional attacker data volume. Evidence is limited to advisory-level detail.
Mitigation direction
Upgrade nats-server to 2.11.15, 2.12.6, or later.
Disable WebSockets if they are not required.
Restrict WebSockets listener access to trusted networks.
Review Red Hat advisories if using packaged downstream products.
Monitor vendor guidance for any additional operational mitigations.
Validation and detection
Inventory nats-server versions across production and edge deployments.
Confirm whether WebSockets are enabled in NATS configuration.
Verify WebSockets ports are not exposed to untrusted networks.
Check package status against Red Hat errata where applicable.
Review memory and connection telemetry for abnormal WebSockets traffic.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.