🚨 [security] Update body-parser 1.19.0 → 1.20.6 (minor)

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

1.20.1 (from changelog)

• deps: qs@6.11.0
• perf: remove unnecessary object clone

1.20.0

• Fix error message for json parse whitespace in strict
• Fix internal error when inflated body exceeds limit
• Prevent loss of async hooks context
• Prevent hanging when request already read
• deps: depd@2.0.0
  • Replace internal eval usage with Function constructor
  • Use instance methods on process to check for listeners
• deps: http-errors@2.0.0
  • deps: depd@2.0.0
  • deps: statuses@2.0.1
• deps: on-finished@2.4.1
• deps: qs@6.10.3
• deps: raw-body@2.5.1
  • deps: http-errors@2.0.0

1.19.2

• deps: bytes@3.1.2
• deps: qs@6.9.7
  • Fix handling of __proto__ keys
• deps: raw-body@2.4.3
  • deps: bytes@3.1.2

1.19.1

• deps: bytes@3.1.1
• deps: http-errors@1.8.1
  • deps: inherits@2.0.4
  • deps: toidentifier@1.0.1
  • deps: setprototypeof@1.2.0
• deps: qs@6.9.6
• deps: raw-body@2.4.2
  • deps: bytes@3.1.1
  • deps: http-errors@1.8.1
• deps: safe-buffer@5.2.1
• deps: type-is@~1.6.18

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

✳️ chart.js (2.9.1 → 2.9.4) · Repo

Security Advisories 🚨

🚨 Prototype pollution in chart.js

This affects the package chart.js before 2.9.4. The options parameter is not properly sanitized when it is processed. When the options are processed, the existing options (or the defaults options) are deeply merged with provided options. However, during this operation, the keys of the object being set are not checked, leading to a prototype pollution.

Release Notes

2.9.4

This is the last release of v2 and focused on fixing bugs identified in the v2.9.3 release.

Bugs Fixed

• #7404 - Preserve prototypes when cloning. Thanks @iddings
• #7587 - Fix docs for external moment.js. Thanks @mojoaxel
• #7853 - Fix box recursion when dimensions are NaN. Thanks @alessandroasm
• #7883 - Fix call stack exception when computing label sizes. Thanks @silentmatt
• #7918 - Prevent global prototype pollution via the merge helper
• #7920 - Use Object.create(null) as merge target, to prevent prototype pollution

2.9.3

Bug Fixes

• #6698 Fix undefined variable
• #6719 Don't make legend empty when fill is false

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@kurkle, @benmccann, and @etimberg).

2.9.2

Bug Fixes

• #6641 IE11 & Edge compatible style injection
• #6655 Backwards compatible default fill for radar charts
• #6660 Improve clipping of line charts when border widths are large
• #6661 When a legend item is clicked, make sure the correct item is hidden
• #6663 Refresh package-lock file to pick up new dependency

Performance

• #6671 Stop unnecessary line calculations

Documentation

• #6643 Combine performance documentation sections

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@nagix, @kurkle, @benmccann, @etimberg and @simonbrunel).

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ bytes (indirect, 3.1.0 → 3.1.2) · Repo · Changelog

Release Notes

3.1.2 (from changelog)

• Fix return value for un-parsable strings

3.1.1 (from changelog)

• Fix "thousandsSeparator" incorrecting formatting fractional part

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

Commits

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

• Release 3.1.2
• build: Node.js@17.4
• build: mocha@9.2.0
• Fix return value for un-parsable strings
• build: Node.js@17.3
• Release 3.1.1
• build: mocha@9.1.3
• build: nyc@15.1.0
• docs: add documentation for "bytes" function
• Fix "thousandsSeparator" incorrecting formatting fractional part
• lint: include code in markdown
• build: nyc@14.1.1
• build: support Node.js 17.x
• docs: add quotes around example in thousandsSeparator
• build: mocha@8.4.0
• build: support Node.js 16.x
• build: support Node.js 15.x
• build: mocha@7.2.0
• build: eslint@7.32.0
• build: support Node.js 14.x
• build: support Node.js 13.x
• build: eslint@6.8.0
• build: mocha@6.2.3
• build: eslint@5.16.0
• build: nyc@13.3.0
• build: support Node.js 12.x
• build: Node.js@11.15
• build: Node.js@10.24
• build: use GitHub Actions instead of Travis CI
• build: Node.js@11.9
• build: nyc@13.2.0
• build: eslint@5.13.0
• docs: fix npm version badge

↗️ raw-body (indirect, 2.4.0 → 2.5.3) · Repo · Changelog

Release Notes

2.5.3

What's Changed

Dependencies

• deps: http-errors@2.0.1 by @bjohansebas in #126
  • deps: statuses@2.0.2
  • deps: use tilde notation for dependencies
• deps: use tilde notation for dependencies by @bjohansebas in #126

Documentation

• chore: remove history.md and security.md from being packaged on publish (#122) by @bjohansebas in #129

Other changes

• ci: restore ci for v2 by @bjohansebas in #127
• release 2.5.3 by @bjohansebas in #130

Full Changelog: 2.5.2...2.5.3

2.5.2 (from changelog)

• Fix error message for non-stream argument

2.5.1 (from changelog)

• Fix error on early async hooks implementations

2.5.0 (from changelog)

• Prevent loss of async hooks context
• Prevent hanging when stream is not readable
• deps: http-errors@2.0.0
  • deps: depd@2.0.0
  • deps: statuses@2.0.1

2.4.3 (from changelog)

• deps: bytes@3.1.2

2.4.2 (from changelog)

• deps: bytes@3.1.1
• deps: http-errors@1.8.1
  • deps: setprototypeof@1.2.0
  • deps: toidentifier@1.0.1

2.4.1 (from changelog)

• deps: http-errors@1.7.3
  • deps: inherits@2.0.4

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 call-bind-apply-helpers (added, 1.0.2)

🆕 call-bound (added, 1.0.4)

🆕 dunder-proto (added, 1.0.1)

🆕 es-define-property (added, 1.0.1)

🆕 es-errors (added, 1.3.0)

🆕 es-object-atoms (added, 1.1.2)

🆕 get-intrinsic (added, 1.3.0)

🆕 get-proto (added, 1.0.1)

🆕 gopd (added, 1.2.0)

🆕 hasown (added, 2.0.4)

🆕 math-intrinsics (added, 1.1.0)

🆕 side-channel (added, 1.1.1)

🆕 side-channel-list (added, 1.0.1)

🆕 side-channel-map (added, 1.0.1)

🆕 side-channel-weakmap (added, 1.0.2)

🗑️ emoji-regex (removed)

---

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)