🚨 [security] [boilerplate/ts/infra/rest/express] Update body-parser 1.20.1 → 1.20.6 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ body-parser (1.20.1 → 1.20.6) · Repo · Changelog

Security Advisories 🚨

🚨 body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement

Impact

When body-parser is configured with an invalid limit option value, such as an unparseable string or NaN, bytes.parse() returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service.

This issue affects applications that pass a programmatically computed or user-configurable value to the limit option without validating it first.

Patches

This issue is fixed in body-parser@2.3.0 and body-parser@1.20.6 via #698. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement. null and undefined continue to fall back to the default limit (100kb).

Workarounds

Validate limit before passing it to body-parser. For example, parse the value with bytes.parse() at startup and reject any configuration where it returns null or a non-finite number.

References

• #698: fix PR
• bytes.js: limit parser

🚨 body-parser vulnerable to denial of service when url encoding is enabled

Impact

body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service.

Patches

this issue is patched in 1.20.3

References

Release Notes

1.20.6

Important: Security

• Security fix for CVE-2026-12590 (GHSA-v422-hmwv-36x6)

What's Changed

• fix: improve limit option validation by @Phillip9587 in #741

Full Changelog: 1.20.5...1.20.6

1.20.5

What's Changed

The reason for this release is a fix to the extended urlencoded parser returning objects instead of arrays for large array inputs (> 100) on qs@6.14.2+. (#716)

• refactor(json): simplify strict mode error string construction by @jonchurch in #692
• fix: correct off-by-one error in parameterCount by @abhu85 in #716
• deps(qs): bump qs to 6.15.1 by @jonchurch in #722
• Release: 1.20.5 by @jonchurch in #721

New Contributors

• @abhu85 made their first contribution in #716

Special thanks to triager @krzysdz for keeping this on our radar and effectively triaging the specific issue!

Full Changelog: 1.20.4...1.20.5

1.20.4

What's Changed

• Remove redundant depth check by @blakeembrey in #538
• ci: add support for Node.js v23 by @Phillip9587 in #553
• ci: restore CI for 1.x branch by @bjohansebas in #665
• deps: qs@^6.14.0 by @bjohansebas in #664
• deps: use tilde notation and update certain dependencies by @Phillip9587 in #668
• chore: remove SECURITY.md by @Phillip9587 in #669
• ci: add CodeQL (SAST) by @Phillip9587 in #670
• Release: 1.20.4 by @UlisesGascon in #672

Full Changelog: 1.20.3...1.20.4

1.20.3

What's Changed

Important

• deps: qs@6.13.0
• add depth option to customize the depth level in the parser
• IMPORTANT: The default depth level for parsing URL-encoded data is now 32 (previously was Infinity). Documentation

Other changes

• chore: add support for OSSF scorecard reporting by @inigomarquinez in #522
• ci: fix errors in ci github action for node 8 and 9 by @inigomarquinez in #523
• fix: pin to node@22.4.1 by @wesleytodd in #527
• deps: qs@6.12.3 by @melikhov-dev in #521
• Add OSSF Scorecard badge by @bjohansebas in #531
• Linter by @UlisesGascon in #534
• Release: 1.20.3 by @UlisesGascon in #535

New Contributors

• @inigomarquinez made their first contribution in #522
• @melikhov-dev made their first contribution in #521
• @bjohansebas made their first contribution in #531
• @UlisesGascon made their first contribution in #534

Full Changelog: 1.20.2...1.20.3

1.20.2

• Fix strict json error message on Node.js 19+
• deps: content-type@~1.0.5
  • perf: skip value escaping when unnecessary
• deps: raw-body@2.5.2

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 43 commits:

• 1.20.6 (#746)
• fix: improve limit option validation (#741)
• release(patch): 1.20.5
• deps(qs): bump qs to 6.15.1
• fix: correct off-by-one error in parameterCount (#716)
• deps: qs@~6.14.1 (#690)
• refactor(json): simplify strict mode error string construction (#692)
• 1.20.4 (#672)
• ci: add CodeQL (SAST) (#670)
• chore: remove SECURITY.md (#669)
• deps: use tilde notation and update certain dependencies (#668)
• deps: qs@~6.14.0 (#664)
• ci: restore CI for 1.x branch (#665)
• ci: add support for Node.js v23 (#553)
• Remove redundant depth check (#538)
• 1.20.3
• chore: linter (#534)
• Merge commit from fork
• add scorecard to readme (#531)
• deps: qs@6.12.3 (#521)
• fix: pin to node@22.4.1
• ci: fix errors in ci github action for node 8 and 9 (#523)
• chore: add support for OSSF scorecard reporting (#522)
• 1.20.2
• Fix strict json error message on Node.js 19+
• deps: raw-body@2.5.2
• build: eslint@8.34.0
• build: Node.js@18.14
• build: Node.js@14.21
• deps: content-type@~1.0.5
• build: eslint-plugin-promise@6.1.1
• build: supertest@6.3.3
• build: mocha@10.2.0
• build: eslint-plugin-import@2.27.5
• build: eslint@8.32.0
• build: Node.js@16.19
• docs: switch badges to badgen
• build: Node.js@18.13
• build: actions/download-artifact@v3
• build: use $GITHUB_OUTPUT for environment list
• build: actions/upload-artifact@v3
• build: actions/checkout@v3
• build: mocha@10.1.0

↗️ @​bitloops/bl-boilerplate-core (indirect, 0.1.0 → 0.1.1) · Repo

Sorry, we couldn't find anything useful about this release.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)