CVE Vulnerabilities

CVE-2026-48779

Uncontrolled Resource Consumption

Published: Jun 17, 2026 | Modified: Jul 02, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

NameVendorStart VersionEnd Version
WsWs_project1.1.0 (including)5.2.5 (excluding)
WsWs_project6.0.0 (including)6.2.4 (excluding)
WsWs_project7.0.0 (including)7.5.11 (excluding)
WsWs_project8.0.0 (including)8.21.0 (excluding)
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1782840519*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1782839981*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1782839193*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-rhel9:1782838753*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-pf4-rhel9:1782839279*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-pf5-rhel9:1782840539*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-rhel9:1782841925*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-pf5-rhel9:1782844225*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-pf6-rhel9:1782839658*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-rhel9:1782838476*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9:1782839996*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:1782839494*
Red Hat Developer Hub 1.9RedHatrhdh/rhdh-hub-rhel9:1782761244*
Red Hat Discovery 2RedHatdiscovery/discovery-ui-rhel9:1782166952*
Red Hat OpenShift Service Mesh 2.6RedHatopenshift-service-mesh/kiali-ossmc-rhel8:1781937133*
Red Hat OpenShift Service Mesh 2.6RedHatopenshift-service-mesh/kiali-rhel8:1782287580*
Red Hat OpenShift Service Mesh 3.0RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1782201894*
Red Hat OpenShift Service Mesh 3.0RedHatopenshift-service-mesh/kiali-rhel9:1782201833*
Red Hat OpenShift Service Mesh 3.1RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1782201696*
Red Hat OpenShift Service Mesh 3.1RedHatopenshift-service-mesh/kiali-rhel9:1782201537*
Red Hat OpenShift Service Mesh 3.2RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1782201851*
Red Hat OpenShift Service Mesh 3.2RedHatopenshift-service-mesh/kiali-rhel9:1782201812*
Red Hat OpenShift Service Mesh 3.3RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1782231869*
Red Hat OpenShift Service Mesh 3.3RedHatopenshift-service-mesh/kiali-rhel9:1782201466*

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References