Repository navigation
fix(deps-dev): bump body-parser from 2.3.0 to 2.4.0 - #715
Merged
Merged
Conversation
Fixes GHSA-27r3-jxmh-p828, a denial of service when a compressed request body is followed by trailing bytes (affects >= 2.0.0, < 2.4.0). body-parser is only reached through express, which is a dev dependency, so nothing here ships to package consumers. Lockfile-only change: express still asks for ^2.3.0, which allows 2.4.0. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
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.
Upstream behaviour
body-parser
>= 2.0.0, < 2.4.0is affected by GHSA-27r3-jxmh-p828 (CVE-2026-111181, high, CVSS 7.5): a compressed request body followed by trailing bytes can cause a denial of service. It is fixed in 2.4.0.npm auditflagged the lockfile's[email protected], which is pulled in by[email protected].Change
Lockfile only:
body-parser2.3.0 to 2.4.0, plus the three dependency ranges 2.4.0 itself declares (content-type,iconv-lite,qs). The installed versions of those three already satisfy the new ranges, so no other package changes.package.jsonis untouched;expressasks for^2.3.0, which allows 2.4.0.expressis a dev dependency, so nothing here ships to package consumers.Done with
npm update body-parserrather thannpm audit fix, becauseaudit fixalso bumpsminimatch10.2.5 to 10.2.6, which stays inside the vulnerable range and fixes nothing.Not in this PR
minimatch(GHSA-g3hv-75wg-m249, medium, dev-only viatypedoc) is still open. The patched release is 11.0.1, and forcing it with an override makestypedoc0.28.20 crash (mini.matchOne is not a function). Tracked upstream in TypeStrong/typedoc#3150, with the fix in TypeStrong/typedoc#3151. Waiting on a typedoc release.Verification
npm audit: thebody-parserfinding is gone. Only theminimatchone remains.npm run typecheckandnpm run build: clean.npm test: 194 files, 4218 passed, 1 skipped, same asmain.🤖 Generated with Claude Code