Skip to content

fix: bump qs minimum to ^6.14.2 for CVE-2026-2391 - #7057

Merged
bjohansebas merged 1 commit into
expressjs:masterfrom
davetashner:fix/cve-2026-2391-qs
Feb 22, 2026
Merged

bjohansebas merged 1 commit into
expressjs:masterfrom
davetashner:fix/cve-2026-2391-qs

Conversation

@davetashner

Copy link
Copy Markdown
Contributor

Summary

Bumps the qs dependency minimum from ^6.14.1 to ^6.14.2 to address CVE-2026-2391 / GHSA-w7fw-mjwx-w883.

Vulnerability: qs versions before 6.14.2 have an arrayLimit bypass in comma parsing that allows denial of service.

While the existing ^6.14.1 semver range already resolves to 6.14.2+ on fresh installs, bumping the minimum ensures:

  • The vulnerable version cannot be pinned or resolved via lockfiles
  • npm audit no longer flags express installations

Changes

  • package.json: "qs": "^6.14.1" → "qs": "^6.14.2" (1 line)

Test plan

  • npm run lint passes
  • npm test passes (1,244 tests)
  • qs@6.15.0 resolved and installed successfully (compatible with ^6.14.2)

qs versions before 6.14.2 have an arrayLimit bypass in comma parsing
that allows denial of service (GHSA-w7fw-mjwx-w883).

While the existing ^6.14.1 semver range allows 6.14.2 on fresh
installs, bumping the minimum ensures the vulnerable version cannot
be resolved.

Signed-off-by: davetashner <5702882+davetashner@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

@bjohansebas bjohansebas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM,thanks!

@bjohansebas
bjohansebas merged commit 925a1df into expressjs:master Feb 22, 2026
28 checks passed
@davetashner
davetashner deleted the fix/cve-2026-2391-qs branch February 22, 2026 03:19
@Joaovtrc

Copy link
Copy Markdown

Any date for this to be released?

@ctcpip

ctcpip commented Mar 20, 2026

Copy link
Copy Markdown
Member

it doesn't need to be released. package.json had "qs": "^6.14.1",, which means users will get the newer version when installing express, or using npm update or npm audit fix on an existing project

@Joaovtrc

Copy link
Copy Markdown

it doesn't need to be released. package.json had "qs": "^6.14.1",, which means users will get the newer version when installing express, or using npm update or npm audit fix on an existing project

I see! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants