Skip to content

[agent] chore(deps): bump ws to ^8.21.0 via overrides (GHSA-96hv-2xvq-fx4p)#792

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/dependabot-ws-8.21.0-db40ccb1a87b69e4
Draft

[agent] chore(deps): bump ws to ^8.21.0 via overrides (GHSA-96hv-2xvq-fx4p)#792
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/dependabot-ws-8.21.0-db40ccb1a87b69e4

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

Adds an npm overrides entry to force ws to ^8.21.0, resolving a high-severity memory exhaustion DoS vulnerability in the transitive ws dependency.

Vulnerability

Impact

A peer can send high volumes of tiny fragments/data chunks to force the remote peer into allocating structural wrappers consuming far more memory than the documented message-size limit, leading to OOM termination.

Changes

  • package.json: Added "overrides": { "ws": "^8.21.0" }
  • package-lock.json: Updated ws from 8.18.08.21.0

Why overrides?

ws is a transitive dependency pulled in by jsdom@^24.1.3 (devDependency in packages/mql-typescript). jsdom@24.1.3 requires ws@^8.18.0 — no release in the jsdom@24.x range has updated this constraint to require ws >= 8.21.0. Upgrading jsdom to a version that drops ws entirely (v29+) would be a major breaking change. Therefore, an npm overrides entry is the appropriate remediation to ensure the patched ws version is resolved.

Generated by Dependabot remediation agent · ● 1.1M ·

Add npm overrides to force ws >= 8.21.0, resolving the memory exhaustion
DoS vulnerability (CVE-2026-48779 / GHSA-96hv-2xvq-fx4p) in the transitive
dependency pulled in by jsdom@^24.1.3.

jsdom@24.1.3 declares ws@^8.18.0; no jsdom v24.x release has updated this
range to require ws >= 8.21.0, so an npm override is used as the appropriate
fallback.

Fixes Dependabot alert #277.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants