# CVE-2026-48779: ws: Memory exhaustion DoS from tiny fragments and data chunks > Attackers can cause memory exhaustion and process termination by sending tiny WebSocket fragments, requiring library upgrades to mitigate. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Jun 2026 - **Updated:** 11 Sep 2026 - **Also known as:** AZL-91415, CLEANSTART-2026-PK38447, CLSA-2026-1784769503, CLSA-2026-1784769533, CLSA-2026-1784769619, CLSA-2026-1784856221, CLSA-2026-1785117461, CLSA-2026-1785117464, CLSA-2026-1785204342, CLSA-2026-1785204343, CLSA-2026-1785204378, CLSA-2026-1790161419, CLSA-2026-1792163981, CLSA-2026-1792164080, CVE-2026-62389, DEBIAN-CVE-2026-48779, ECHO-63b9-3484-977b, GHSA-96hv-2xvq-fx4p, MINI-234h-9p6f-58m4, MINI-254m-9647-5x7j, MINI-2p43-m25g-xqxf, MINI-3667-xxp4-7x6v, MINI-3842-p4vc-ppxw, MINI-3m68-mcq2-2x2r, MINI-3mpq-rc94-rf7h, MINI-46p9-rmcj-g3qf, MINI-64cc-9p7g-35f8, MINI-6g5g-cr73-6p6p, MINI-75mq-ggx6-fqrm, MINI-7f36-2wvm-wmp3, MINI-7hg7-xq39-5vg9, MINI-7r9x-c8rc-8vr5, MINI-84gf-h45v-6pqx, MINI-8qxh-crwc-j685, MINI-9354-rv5m-mg83, MINI-9524-pw68-g44m, MINI-9qqj-g4jx-xccx, MINI-9w33-j8fv-h9wr, MINI-9w68-4f32-mhcj, MINI-c79g-gp2j-5j84, MINI-f5cm-rhjj-9mwq, MINI-ff8r-g953-33mg, MINI-g2cx-4f6h-4xrp, MINI-ggwf-3mqw-3j3r, MINI-hc52-fv33-cwvf, MINI-jxm9-7qpq-whfj, MINI-mcjc-x4vh-q763, MINI-mcw8-pvcx-3qr2, MINI-mf8g-xcjh-9c9c, MINI-mhjx-vrw9-4q8w, MINI-pf8x-pxrg-98mx, MINI-pp29-7c54-wmx8, MINI-r44g-q3h2-vcwf, MINI-rf26-7974-89q5, MINI-rg72-48vr-37v6, MINI-rq5p-c593-334x, MINI-rwpv-qjr3-g8jm, MINI-vm67-jx3v-vx56, MINI-w657-2jgj-jv4x, MINI-xhx7-8whr-5rwc, ROOT-APP-NPM-CVE-2026-48779, UBUNTU-CVE-2026-48779, openSUSE-SU-2026:11123-1, openSUSE-SU-2026:11137-1, openSUSE-SU-2026:11138-1, openSUSE-SU-2026:11354-1, openSUSE-SU-2026:11397-1 ## What is CVE-2026-48779? CVE-2026-48779 is a high-severity denial of service vulnerability in websockets ws, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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: CWE-1050 (Excessive Platform Resource Consumption within a Loop), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-48779? 8 open source packages ship an affected version, including ws. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ws` | npm | From 1.1.0 | 5.2.5 | | `ws` | npm | From 1.1.0 | 5.2.5 | | `ws` | npm | From 6.0.0 | 6.2.4 | | `ws` | npm | From 6.0.0 | 6.2.4 | | `ws` | npm | From 7.0.0 | 7.5.11 | | `ws` | npm | From 7.0.0 | 7.5.11 | | `ws` | npm | From 8.0.0 | 8.21.0 | | `ws` | npm | From 8.0.0 | 8.21.0 | | `python-bqplot` | openSUSE:Tumbleweed | All versions | 0.13.1-15.1 | | `python-ipympl` | openSUSE:Tumbleweed | All versions | 0.10.0-18.1 | | `python-jupyter-ydoc` | openSUSE:Tumbleweed | All versions | 3.5.0-1.1 | | `python-jupyterlab-templates` | openSUSE:Tumbleweed | All versions | 0.5.3-2.1 | | `python-nbclassic` | openSUSE:Tumbleweed | All versions | 1.3.3-2.1 | Products: Ws Project Ws. ## How do I fix CVE-2026-48779? Upgrade ws to a fixed version for your release line: 5.2.5, 6.2.4, 7.5.11 or 8.21.0. ## Is CVE-2026-48779 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48779 exists. ## Other vulnerabilities in websockets ws - [CVE-2016-10518](https://insights.sbomify.com/CVE-2016-10518/): Remote Memory Disclosure in ws (high 7.5) - [CVE-2016-10542](https://insights.sbomify.com/CVE-2016-10542/): DoS due to excessively large websocket message in ws (high 7.5) - [CVE-2026-45736](https://insights.sbomify.com/CVE-2026-45736/): ws: Uninitialized memory disclosure (medium 4.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-48779 and fix it if it is affected. What it is: CVE-2026-48779 is a high-severity denial of service vulnerability in websockets ws, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48779 exists. Affected packages and fixed versions: - ws (npm): affected from 1.1.0; fixed in 5.2.5 - ws (npm): affected from 1.1.0; fixed in 5.2.5 - ws (npm): affected from 6.0.0; fixed in 6.2.4 - ws (npm): affected from 6.0.0; fixed in 6.2.4 - ws (npm): affected from 7.0.0; fixed in 7.5.11 - ws (npm): affected from 7.0.0; fixed in 7.5.11 - ws (npm): affected from 8.0.0; fixed in 8.21.0 - ws (npm): affected from 8.0.0; fixed in 8.21.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-48779/ (Markdown: https://insights.sbomify.com/CVE-2026-48779/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48779 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48779 - OSV: https://osv.dev/vulnerability/CVE-2026-48779 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-48779/ Summaries are generated and may contain mistakes; the official description above is the record.