Skip to content

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

Open
depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/npm/body-parser-1.20.6
Open

depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/npm/body-parser-1.20.6

Conversation

@depfu

@depfu depfu Bot commented Jul 21, 2026 •

Copy link
Copy Markdown
Contributor

🚨 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

🚨 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

More info than we can show here.

1.20.5

More info than we can show here.

1.20.4

More info than we can show here.

1.20.3

More info than we can show here.

1.20.2

More info than we can show here.

1.20.1 (from changelog)

More info than we can show here.

1.20.0

More info than we can show here.

1.19.2

More info than we can show here.

1.19.1

More info than we can show here.

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)

More info than we can show here.

3.1.1 (from changelog)

More info than we can show here.

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.

↗️ content-type (indirect, 1.0.4 → 1.0.5) · Repo · Changelog

Release Notes

1.0.5

More info than we can show here.

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.

↗️ function-bind (indirect, 1.1.1 → 1.1.2) · Repo · Changelog

Commits

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

↗️ get-intrinsic (indirect, 1.1.1 → 1.3.0) · Repo · Changelog

Release Notes

1.3.0 (from changelog)

More info than we can show here.

1.2.7 (from changelog)

More info than we can show here.

1.2.6 (from changelog)

More info than we can show here.

1.2.5 (from changelog)

More info than we can show here.

1.2.4 (from changelog)

More info than we can show here.

1.2.3 (from changelog)

More info than we can show here.

1.2.2 (from changelog)

More info than we can show here.

1.2.1 (from changelog)

More info than we can show here.

1.2.0 (from changelog)

More info than we can show here.

1.1.3 (from changelog)

More info than we can show here.

1.1.2 (from changelog)

More info than we can show here.

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.

↗️ has-symbols (indirect, 1.0.2 → 1.1.0) · Repo · Changelog

Release Notes

1.1.0 (from changelog)

More info than we can show here.

1.0.3 (from changelog)

More info than we can show here.

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.

↗️ object-inspect (indirect, 1.11.0 → 1.13.4) · Repo · Changelog

Release Notes

1.13.4 (from changelog)

More info than we can show here.

1.13.3 (from changelog)

More info than we can show here.

1.13.2 (from changelog)

More info than we can show here.

1.13.1 (from changelog)

More info than we can show here.

1.13.0 (from changelog)

More info than we can show here.

1.12.3 (from changelog)

More info than we can show here.

1.12.2 (from changelog)

More info than we can show here.

1.12.1 (from changelog)

More info than we can show here.

1.12.0 (from changelog)

More info than we can show here.

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.

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

Release Notes

2.5.3

More info than we can show here.

2.5.2 (from changelog)

More info than we can show here.

2.5.1 (from changelog)

More info than we can show here.

2.5.0 (from changelog)

More info than we can show here.

2.4.3 (from changelog)

More info than we can show here.

2.4.2 (from changelog)

More info than we can show here.

2.4.1 (from changelog)

More info than we can show here.

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.

↗️ side-channel (indirect, 1.0.4 → 1.1.1) · Repo · Changelog

Release Notes

1.1.1 (from changelog)

More info than we can show here.

1.1.0 (from changelog)

More info than we can show here.

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-proto (added, 1.0.1)

🆕 gopd (added, 1.2.0)

🆕 hasown (added, 2.0.4)

🆕 math-intrinsics (added, 1.1.0)

🆕 side-channel-list (added, 1.0.1)

🆕 side-channel-map (added, 1.0.1)

🆕 side-channel-weakmap (added, 1.0.2)


Depfu Status

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)

This change is Reviewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants