chore: upgrade qs to ^6.16.0 to address CVE-2026-82417, CVE-2026-82562 - #1627
Open
claude[bot] wants to merge 2 commits into
Open
chore: upgrade qs to ^6.16.0 to address CVE-2026-82417, CVE-2026-82562#1627claude[bot] wants to merge 2 commits into
claude[bot] wants to merge 2 commits into
Conversation
Raises the existing `qs` resolution floor from ^6.14.2 to ^6.16.0 so every requester resolves to 6.16.0, which is no longer affected by the stringify TypeError and array-limit bypass advisories. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
License Audit❌ Audit failed to produce results. Check the workflow logs for details. |
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.
Fixes SOU-2127
Fixes SOU-2128
Summary
qsresolved to6.15.2, which is affected by two advisories. The repo already carries aqsresolution, but its floor of^6.14.2still admitted the vulnerable version. This raises the floor to^6.16.0.Advisories addressed
qs.stringifythrows aTypeErroron objects with a non-callableconstructor.isBufferarrayLimitbypass fora[]=keys when parsing withcomma: trueandthrowOnLimitExceeded: trueBoth are fixed in
6.16.0.Verification
yarn why qsreports every requester (@gitbeaker/core,@gitbeaker/requester-utils,body-parser@1.20.6,body-parser@2.3.0,express@4.22.2,express@5.2.1,typed-rest-client) resolving toqs@npm:6.16.0. No affected version remains in the graph.yarn install --immutablesucceeds.yarn build:depssucceeds.yarn testpasses (2153 tests across queryLanguage, shared, backend, and web).🤖 Generated with Claude Code
Note
Low Risk
Transitive dependency pin with no application code changes; typical low-risk security patch bump.
Overview
Raises the Yarn
resolutionsfloor forqsfrom^6.14.2to^6.16.0, so the lockfile no longer resolves6.15.2and instead pinsqs@6.16.0across transitive consumers (e.g. Express/body-parser, GitBeaker).This is a dependency-only change to address CVE-2026-82417 (
stringify/constructor.isBuffer) and CVE-2026-82562 (DoS viaarrayLimitbypass withcomma: true). The lockfile also picks upqs’s updatedside-channel/side-channel-listentries.Reviewed by Cursor Bugbot for commit 15c49d2. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by cubic
Raises the existing
qsresolution floor from^6.14.2(which resolved to vulnerable6.15.2) to^6.16.0, fixing SOU-2127 and SOU-2128. The upgrade addresses theqs.stringifyTypeErrorandarrayLimitdenial-of-service bypass without application-code changes.side-channeldependencies so every requester resolves toqs@6.16.0.Written for commit 15c49d2. Summary will update on new commits.