deps: bump body-parser to ^2.3.0 to fix CVE-2026-12590#7390
Open
Mayvis wants to merge 1 commit into
Open
Conversation
body-parser < 2.3.0 silently disables request body size enforcement when given an invalid `limit` option value (bytes.parse() returns null), allowing a denial of service via arbitrarily large payloads (CVE-2026-12590 / GHSA-v422-hmwv-36x6). 2.3.0 throws on invalid `limit` values at parser initialization instead of failing open. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
body-parserfrom^2.2.1to^2.3.0to remediate CVE-2026-12590 (GHSA-v422-hmwv-36x6).body-parser
>=2.0.0 <2.3.0(and<1.20.6on the 1.x line) fails open whengiven an invalid
limitoption value:bytes.parse()returnsnull, whichsilently disables request body size enforcement and allows a denial of service
via arbitrarily large payloads. body-parser 2.3.0 (expressjs/body-parser#698)
now throws on an invalid
limitat parser initialization instead of ignoring it.Express's existing
^2.2.1range technically already permits 2.3.0, butdeclaring
^2.3.0makes the security intent explicit and ensures consumers(and scanners like Trivy) resolve to the patched release.
Changes
package.json:body-parser^2.2.1→^2.3.0History.md: changelog entry under Unreleased → 🚀 ImprovementsTesting
body-parser-backed middleware tests pass (211 passing):express.json,express.urlencoded,express.raw,express.text.References