[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.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[maxigimenez]

Security triage: Tier B — ready for review, not for auto-merge

This PR closes the Vanta finding for Dependabot alert 181.

What and why

package	from	to	severity	via
body-parser	2.3.0	2.4.0	HIGH	@modelcontextprotocol/sdk → express

• GHSA-27r3-jxmh-p828 / CVE-2026-111181, HIGH
• Vanta remediateByDate: 2026-11-26 — 29 days remaining
• Affected range: >= 2.0.0, < 2.4.0

Advisory title, verbatim: "body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body."

Exposure

Runtime. npm ls body-parser on main:

@currents/mcp@2.7.0
`-- @modelcontextprotocol/sdk@1.32.0
  `-- express@5.2.1
    `-- body-parser@2.4.0

express is how the HTTP host (src/host/httpServer.ts) serves requests, so this reaches the published @currents/mcp package and the Docker image. Any deployment running start:http parses request bodies through it.

The fix

Transitive, through a lockfile refresh. express@5.2.1 requires body-parser@^2.2.1, which 2.4.0 satisfies, so no manifest edit is needed. The diff also carries the dependency ranges body-parser itself moved: content-type 2.0.0 → 2.1.0, iconv-lite 0.7.2 → 0.7.3, qs 6.16.0 → 6.17.0.

Breaking-change check

From HISTORY.md for 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)

No removals or breaking changes. One thing to note rather than a blocker: 2.4.0 is a minor with a new feature, not a pure patch. The zstd support degrades to a 415 on Node below 22.15, and test.yml covers Node 20.x, so that path stays as it is today on Node 20.

Verification

CI on head 0c01378 — all three jobs success:

• Test (Node 20.x)
• Test (Node 22.x)
• Test (Node 24.x)

I did not check this branch out and run the suite locally, so this is Dependabot's green, not mine.

CI coverage

Triggers test.yml only (pull_request → main, no paths filter). The publish and release workflows are workflow_dispatch and do not run here.

Why this is not auto-merged

Tier A auto-merge is restricted to changes where every entry is development-scope. body-parser resolves under dependencies and ships in the published package and the Docker image, so it stays with a human regardless of how green CI is.

What a human should still check

1. That the qs 6.16.0 → 6.17.0 bump carried here does not collide with chore(deps): bump qs from 6.16.0 to 6.17.0 in /mcp-server #247, which makes the same move on its own. Whichever merges second will need a rebase.
2. Whether the zstd behaviour change matters for any deployment pinned below Node 22.15.

Needs release

@currents/mcp is published to npm. This is a runtime fix, so it reaches users only on the next release of the package — currently 2.7.0. Flagging, not publishing.

---

Generated by Claude Code