Update websocket-driver to 0.7.5

[Copilot]

Track translation progress by opening a draft PR using this template and checking off the translations completed

Each lesson includes a translation of the README.md and the Assignment.md file, if available. Only mark the lesson complete if both those files are translated per lesson, please.

• 1

• 1-1

• 1-2

• 1-3

• 2

• 2-1

• 2-2

• 2-3

• 2-4

• 3

• 3-1

• 3-2

• 3-3

• 4

• 4-1

• 5

• 5-1

• 5-2

• 5-3

• 6

• 6-1

• 6-2

• 6-3

• 6-4

• 6-5

• 6-6

• 7

• 7-1

• 7-2

• 7-3

• 7-4

• Quiz (add a file in the quiz-app with all localizations)

Summary

websocket-driver@0.7.4 permits message corruption through oversized draft-protocol length headers (CVE-2026-54466). This updates the affected transitive dependency to the lowest patched version, 0.7.5.

Changes

• Updated the solution project’s npm lockfile using npm.
• Preserved the existing direct dependencies and dependency constraints.
• Limited the diff to websocket-driver resolution and package metadata.

Reachability Assessment

Reachable during development — high confidence.

@vue/cli-service loads webpack-dev-server → sockjs → faye-websocket → websocket-driver. SockJS constructs the Faye WebSocket transport, exposing the affected parser while npm run serve accepts WebSocket traffic.

Application source does not call WebSocket APIs directly, and this development-only dependency is excluded from the production runtime.

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>websocket-driver: Message corruption via abuse of protocol length headers</alert_title>
<alert_description>### Impact

The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer. Since JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly.

Patches

The issue has been patched in version 0.7.5 by rejecting the message if the length header exceeds the configured maximum message length. All users should upgrade to this version.

Workarounds

No known workarounds exist.

Acknowledgements

This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.</alert_description>

critical
GHSA-xv26-6w52-cph6, CVE-2026-54466
websocket-driver
npm
<vulnerable_versions>0.7.4</vulnerable_versions>
<patched_version>0.7.5</patched_version>
<manifest_path>3-Data-Visualization/13-meaningful-visualizations/solution/package-lock.json</manifest_path>

https://github.com/faye/websocket-driver-node/security/advisories/GHSA-xv26-6w52-cph6 https://github.com/faye/websocket-driver-node/releases/tag/0.7.5 https://github.com/advisories/GHSA-xv26-6w52-cph6

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in th...

• Resolves microsoft/Data-Science-For-Beginners alert updated tracking links #435

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• 3-Data-Visualization/13-meaningful-visualizations/solution/package-lock.json: Generated file

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• 3-Data-Visualization/13-meaningful-visualizations/solution/package-lock.json: Generated file

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (2)

• 3-Data-Visualization/13-meaningful-visualizations/starter/package-lock.json: Generated file
• quiz-app/package-lock.json: Generated file