Bump socket.io-parser from 4.2.4 to 4.2.7 - #2682
Conversation
Bumps [socket.io-parser](https://github.com/socketio/socket.io) from 4.2.4 to 4.2.7. - [Release notes](https://github.com/socketio/socket.io/releases) - [Changelog](https://github.com/socketio/socket.io/blob/main/CHANGELOG.md) - [Commits](https://github.com/socketio/socket.io/compare/socket.io-parser@4.2.4...socket.io-parser@4.2.7) --- updated-dependencies: - dependency-name: socket.io-parser dependency-version: 4.2.7 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Hello dependabot[bot],My role is to assist you with the merge of this Available options
Available commands
Status report is not available. The following options are set: bypass_author_approval, bypass_jira_check |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the The following options are set: bypass_author_approval, bypass_jira_check |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Dependency Bump Evaluation
Version change: socket.io-parser 4.2.4 -> 4.2.7 (patch)
Changes:
- 4.2.5: Bump transitive
debugdependency from ~4.3.1 to ~4.4.1 - 4.2.6: Security fix for CVE-2026-33151 (High severity) — adds a limit to the number of binary attachments to prevent OOM via crafted packets
- 4.2.7: Bug fixes — reject binary packets with zero attachments; honor toJSON() when deconstructing binary packets
Breaking changes: None
Security concerns: This bump fixes CVE-2026-33151 (High). A crafted Socket.IO packet could force the server to buffer an unbounded number of binary attachments, causing out-of-memory. Arsenal uses socket.io for its RPC layer (lib/network/rpc/rpc.ts, sio-stream.ts, level-net.ts) and metadata file server, making it directly exposed. Upgrade is recommended.
Note: npm publisher changed to "GitHub Actions" — standard CI-based publishing for the socketio org, not a supply chain concern.
Impact on codebase: Only yarn.lock is modified. No source code changes required — the parser is a transitive dependency of socket.io and socket.io-client.
Recommendation: SAFE TO MERGE
Notes: CI checks are in progress at time of review. Merge after CI passes.
— Claude Code
1 participant
Bumps socket.io-parser from 4.2.4 to 4.2.7.
Release notes
Sourced from socket.io-parser's releases.
Commits
4054894chore(release): socket.io-parser@4.2.77c6ef57fix(parser): reject binary packets with zero attachments57f1114fix(parser): honor toJSON() when deconstructing a binary packet (#5518)8d2e4f7docs(security): add CVE-2026-59724 and CVE-2026-59725d2d753frefactor(sio): align client file matching in Node.js HTTP serverdfb5ab3fix(sio): prevent uWebSockets.js from serving missing client filesdcbd961perf(eio): optimize polling request body buffering6bb2e7frefactor(sio): internalize base64id dependencya80711arefactor(eio): internalize base64id dependency8bead0fchore: upgrade to TypeScript 6Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for socket.io-parser since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.