[dependabot]

Bumps body-parser from 2.3.0 to 2.4.0.

Release notes

Sourced from body-parser's releases.

v2.4.0

Important: Security

• Security fix for CVE-2026-111181 (GHSA-27r3-jxmh-p828)

What's Changed

• build(deps): bump actions/checkout from 6.0.3 to 7.0.0 by @​dependabot[bot] in expressjs/body-parser#737
• chore: group github actions updates by @​Phillip9587 in expressjs/body-parser#743
• build(deps): bump the github-actions group with 3 updates by @​dependabot[bot] in expressjs/body-parser#745
• test: fix 'presist' typo in test descriptions by @​maxtaran2010 in expressjs/body-parser#749
• docs: include security fix in 2.3.0 changes by @​UlisesGascon in expressjs/body-parser#748
• fix: avoid mutating read options when reading body by @​Phillip9587 in expressjs/body-parser#742
• refactor: move getCharset helper to only usage by @​Phillip9587 in expressjs/body-parser#707
• build(deps): bump the github-actions group with 7 updates by @​dependabot[bot] in expressjs/body-parser#753
• refactor: switch to neostandard by @​Phillip9587 in expressjs/body-parser#751
• perf(json): avoid first-char regex for direct JSON bodies by @​Phillip9587 in expressjs/body-parser#744
• docs: fix entity verify error description by @​Rawal27 in expressjs/body-parser#755
• feat: zstandard support by @​Phillip9587 in expressjs/body-parser#586
• test: remove unused experimentalZstd option by @​Phillip9587 in expressjs/body-parser#757
• ci: run tests on windows and macos matrix by @​kilisamemarisaaa in expressjs/body-parser#759
• deps: qs@^6.16.0 by @​krzysdz in expressjs/body-parser#762
• build(deps): bump the github-actions group with 3 updates by @​dependabot[bot] in expressjs/body-parser#763
• ci: trigger npm publish on release published and set dist-tag by @​UlisesGascon in expressjs/body-parser#768
• build(deps): bump the github-actions group with 3 updates by @​dependabot[bot] in expressjs/body-parser#771
• fix(test): pin supertest to 7.3.0 to avoid 7.3.1 regression by @​saadkhantareen in expressjs/body-parser#773
• perf: inline content stream setup by @​Phillip9587 in expressjs/body-parser#750
• docs: note that req.body may be undefined in v2 by @​Hashim1999164 in expressjs/body-parser#752
• docs: fix strict option description by @​Rawal27 in expressjs/body-parser#756
• docs: fix depth error description by @​johnnyhuirilef in expressjs/body-parser#776
• chore: update dependencies by @​Phillip9587 in expressjs/body-parser#778
• Release: 2.4.0 by @​UlisesGascon in expressjs/body-parser#777

New Contributors

• @​maxtaran2010 made their first contribution in expressjs/body-parser#749
• @​Rawal27 made their first contribution in expressjs/body-parser#755
• @​kilisamemarisaaa made their first contribution in expressjs/body-parser#759
• @​saadkhantareen made their first contribution in expressjs/body-parser#773
• @​Hashim1999164 made their first contribution in expressjs/body-parser#752
• @​johnnyhuirilef made their first contribution in expressjs/body-parser#776

Full Changelog: expressjs/body-parser@v2.3.0...v2.4.0

Changelog

Sourced from body-parser's changelog.

2.4.0

• Security fix for GHSA-27r3-jxmh-p828 (CVE-2026-111181)
• feat: add zstd content-encoding support (#586)
  • Requires Node.js ^22.15.0 or >=23.8.0; older versions keep returning 415 for zstd encoded bodies
• fix: avoid mutating the parser options and the request object while reading the body (#742, #750)
• perf(json): avoid first-char regex for direct JSON bodies (#744)
• deps:
  • content-type@^2.1.0
  • iconv-lite^0.7.3
  • qs@^6.16.1

Commits

• b4744d7 2.4.0 (#777)
• f7075ea fix: prevent process crash from trailing bytes after a compressed body
• 185ff1d chore: update dependencies (#778)
• 73713f7 docs: fix depth error description (#776)
• 2dcc826 docs: improve readability (#756)
• 402dbdc docs: note that req.body may be undefined in v2 (#752)
• 9883a1e perf: inline content stream setup (#750)
• 02101da fix(test): pin supertest to 7.3.0 to avoid 7.3.1 regression (#773)
• 822a0fd build(deps): bump the github-actions group with 3 updates (#771)
• aa9889b ci: trigger npm publish on release published and set dist-tag (#768)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for body-parser since your current version.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/body-parser	2.4.0	🟢 8	Details Check Score Reason Code-Review 🟢 7 Found 18/25 approved changesets -- score normalized to 7 Maintained 🟢 10 23 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Pinned-Dependencies 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Dependency-Update-Tool 🟢 10 update tool detected Vulnerabilities 🟢 10 0 existing vulnerabilities detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected SAST 🟢 9 SAST tool detected but not run on all commits Signed-Releases ⚠️ -1 no releases found Packaging 🟢 10 packaging workflow detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Security-Policy 🟢 10 security policy file detected Branch-Protection ⚠️ 1 branch protection is not maximal on development and all release branches CI-Tests 🟢 9 26 out of 28 merged PRs checked by a CI test -- score normalized to 9 Contributors 🟢 10 project has 33 contributing companies or organizations
npm/content-type	2.1.0	🟢 7.4	Details Check Score Reason Code-Review 🟢 5 Found 17/29 approved changesets -- score normalized to 5 Maintained 🟢 10 12 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 Binary-Artifacts 🟢 10 no binaries found in the repo Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 4 dependency not pinned by hash detected -- score normalized to 4 Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches Signed-Releases ⚠️ -1 no releases found Security-Policy 🟢 9 security policy file detected SAST 🟢 9 SAST tool detected but not run on all commits
npm/qs	6.17.1	🟢 5.8	Details Check Score Reason Code-Review ⚠️ 1 Found 3/28 approved changesets -- score normalized to 1 Maintained 🟢 10 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Binary-Artifacts 🟢 10 no binaries found in the repo Security-Policy 🟢 10 security policy file detected Packaging ⚠️ -1 packaging workflow not detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices 🟢 5 badge detected: Passing Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST ⚠️ -1 internal error: internal error: Client.Checks.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Although you appear to have the correct authorization credentials, the `cursor` organization has an IP allow list enabled, and your IP address is not permitted to access this resource.

Scanned Files

• package-lock.json