chore(deps): bump websocket-driver to 0.7.5 to fix CVE-2026-54466 - #672
Merged
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jirimoravcik
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GHSA-xv26-6w52-cph6 (critical, CVSS 9.2): draft-protocol frame length headers let a client encode an arbitrarily large integer as a run of bytes with the high bit set. The parser accumulates it past 64-bit float precision, so the subsequent payload is framed incorrectly and messages corrupt. Fixed in 0.7.5 by rejecting length headers that exceed the configured maximum message length.
Lockfile-only change:
websocket-driveris a transitive dev dependency offaye-websocket, which declares>=0.5.1, so 0.7.5 satisfies the existing range. Nopackage.jsonedit and nopnpm-workspace.yamloverride are needed, so there is nothing to unwind on a later bump.Nothing published to npm was exposed.
faye-websocketis a devDependency used only by the e2e WebSocket tests; runtimedependenciesare just socks, socks-proxy-agent and tslib, andfilespublishes onlydist.Verified with the full unit + e2e suite on Node 20: 2190 passing, 0 failing, 0 pending.