ws Memory Exhaustion DoS Node.js <5.2.5 6.2.4 7.5.11 8.21.0
CVE-2026-48779 Published on June 16, 2026

ws: Memory exhaustion DoS from tiny fragments and data chunks
ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.

NVD

Vulnerability Analysis

CVE-2026-48779 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. An automatable proof of concept (POC) exploit exists. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
NONE
Integrity Impact:
NONE
Availability Impact:
HIGH

Weakness Types

What is a Resource Exhaustion Vulnerability?

The software does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

CVE-2026-48779 has been classified to as a Resource Exhaustion vulnerability or weakness.

Allocation of Resources Without Limits or Throttling

The software allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.

Excessive Platform Resource Consumption within a Loop

The software has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.


Products Associated with CVE-2026-48779

Want to know whenever a new CVE is published for Red Hat products? stack.watch will email you.

Red Hat Discovery
 
Red Hat Service Mesh
 
Red Hat Cryostat
 
Red Hat Gatekeeper
 
Red Hat Rhmt
 
Red Hat Workload Availability Nhc
 
Red Hat Openshift Lightspeed
 
Red Hat Openshift Pipelines
 
Red Hat Amq Broker
 
Red Hat Ansible Automation Platform
 
Red Hat Apache Camel Hawtio
 
Red Hat Podman Desktop
 
Red Hat Connectivity Link
 
Red Hat Jboss Data Grid
 
Red Hat Rhdh
 
Red Hat Enterprise Linux (RHEL)
 
Red Hat Enterprise Linux Ai
 
Red Hat Jboss Fuse
 
Red Hat Hummingbird
 
Red Hat Openshift Ai
 
Red Hat Openshift
 
Red Hat Openshift Data Foundation
 
Red Hat Openshift Devspaces
 
Red Hat Container Native Virtualization
 
Red Hat Quay
 
Red Hat Satellite
 
Red Hat Trusted Artifact Signer
 
Red Hat Ansible Portal
 
Red Hat Camel Spring Boot
 
Red Hat Build Keycloak
 
Red Hat Jboss Enterprise Application Platform
 
Red Hat Jbosseapxp
 
Red Hat Cluster Observability Operator
 

Affected Versions

websockets ws: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Cluster Observability Operator 1.5.0: Red Hat Developer Hub 1.10: Red Hat Developer Hub 1.9: Red Hat Discovery 2: Red Hat Migration Toolkit 1.8: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.18: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.19: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat Openshift Data Foundation 4.2: Red Hat OpenShift Dev Spaces 3.29: Red Hat OpenShift Dev Spaces 3.29: Red Hat OpenShift Service Mesh 2.6: Red Hat OpenShift Service Mesh 2.6: Red Hat OpenShift Service Mesh 3.0: Red Hat OpenShift Service Mesh 3.0: Red Hat OpenShift Service Mesh 3.1: Red Hat OpenShift Service Mesh 3.1: Red Hat OpenShift Service Mesh 3.2: Red Hat OpenShift Service Mesh 3.2: Red Hat OpenShift Service Mesh 3.3: Red Hat OpenShift Service Mesh 3.3: Red Hat Trusted Artifact Signer 1.4: Red Hat Cryostat 4: Red Hat Cryostat 4: Red Hat Cryostat 4: Red Hat Cryostat 4: Red Hat Gatekeeper 3: Red Hat Node HealthCheck Operator: Red Hat Node HealthCheck Operator: Red Hat Node HealthCheck Operator: Red Hat OpenShift Lightspeed: Red Hat OpenShift Lightspeed: Red Hat OpenShift Lightspeed: Red Hat OpenShift Pipelines: Red Hat OpenShift Pipelines: Red Hat OpenShift Pipelines: Red Hat OpenShift Pipelines: Red Hat OpenShift Pipelines: Red Hat OpenShift Service Mesh 3: Red Hat OpenShift Service Mesh 3: Red Hat AMQ Broker 7: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat Ansible Automation Platform 2: Red Hat build of Apache Camel for Spring Boot 4: Red Hat build of Apache Camel - HawtIO 4: Red Hat Build of Keycloak: Red Hat Build of Podman Desktop: Red Hat Build of Podman Desktop - Tech Preview: Red Hat Build of Podman Desktop - Tech Preview: Red Hat Build of Podman Desktop - Tech Preview: Red Hat Connectivity Link 1: Red Hat Data Grid 8: Red Hat Enterprise Linux 10: Red Hat Enterprise Linux 10: Red Hat Enterprise Linux 10: Red Hat Enterprise Linux 10: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux 9: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Fuse 7: Red Hat Hardened Images: Red Hat Hardened Images: Red Hat Hardened Images: Red Hat Hardened Images: Red Hat Hardened Images: Red Hat Hardened Images: Red Hat JBoss Enterprise Application Platform 8: Red Hat JBoss Enterprise Application Platform Expansion Pack: Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift AI (RHOAI): Red Hat OpenShift Container Platform 4: Red Hat OpenShift Container Platform 4: Red Hat OpenShift Container Platform 4: Red Hat OpenShift Container Platform 4: Red Hat OpenShift Virtualization 4: Red Hat OpenShift Virtualization 4: Red Hat Quay 3: Red Hat Satellite 6: Red Hat Self-service automation portal 2: Red Hat Self-service automation portal 2:

Exploit Probability

EPSS
0.78%
Percentile
52.24%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.