[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
body-parser	1.20.2 → 1.20.9

---

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

CVE-2024-45590 / GHSA-qwcr-r2fm-qrc7

More information

Details

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

Severity

• CVSS Score: 8.7 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

• https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7
• https://github.com/expressjs/body-parser/commit/b2695c4450f06ba3b0ccf48d872a229bb41c9bce
• https://nvd.nist.gov/vuln/detail/CVE-2024-45590
• https://github.com/advisories/GHSA-qwcr-r2fm-qrc7

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

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

CVE-2026-12590 / GHSA-v422-hmwv-36x6

More information

Details

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

Severity

• CVSS Score: 3.7 / 10 (Low)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

References

• https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6
• https://nvd.nist.gov/vuln/detail/CVE-2026-12590
• https://github.com/expressjs/body-parser/pull/698
• https://github.com/expressjs/body-parser/pull/741
• https://github.com/expressjs/body-parser/commit/2322e111cc321413ec2b7b76d01be533d3de9d7d
• https://github.com/expressjs/body-parser/commit/3492672eee593d5c158f239b6e9115498a5dbeac
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/body-parser/releases/tag/1.20.6
• https://github.com/expressjs/body-parser/releases/tag/v2.3.0
• https://github.com/advisories/GHSA-v422-hmwv-36x6

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

CVE-2026-111181 / GHSA-27r3-jxmh-p828

More information

Details

Impact

A single request can crash any application using body-parser with default options. When a request carries a Content-Encoding (for example gzip), body-parser pipes it into a decompression stream and, after reading the body, leaves that stream piped with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No authentication or matching route is required, since parsing runs before routing.

Patches

Fixed in body-parser 2.4.0 and 1.20.9. Upgrade to one of these versions.

Workarounds

Pass inflate: false to the body-parser middleware if the application does not need to accept compressed request bodies. This rejects encoded requests before any decompression stream is created.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
• https://nvd.nist.gov/vuln/detail/CVE-2026-111181
• https://github.com/expressjs/body-parser/commit/1260c3845f54502a05a87594f09a334786bb34d7
• https://github.com/expressjs/body-parser/commit/f7075eae3a84c3473ab4bf0a777da28db208e916
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/body-parser/releases/tag/1.20.9
• https://github.com/expressjs/body-parser/releases/tag/v2.4.0
• https://github.com/advisories/GHSA-27r3-jxmh-p828

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

expressjs/body-parser (body-parser)

v1.20.9

Compare Source

Important: Security

• Security fix for CVE-2026-111181 (GHSA-27r3-jxmh-p828)

What's Changed

• Release: 1.20.9 by @​UlisesGascon in #​779

Full Changelog: expressjs/body-parser@1.20.8...1.20.9

v1.20.8

Compare Source

Important

Same code base as 1.20.7. This was created to test the new release process.

What's Changed

• ci: backport npm-publish workflow from master by @​UlisesGascon in #​769
• 1.20.8 by @​UlisesGascon in #​770

Full Changelog: expressjs/body-parser@1.20.7...1.20.8

v1.20.6

Compare Source

======

• Security fix for GHSA-v422-hmwv-36x6
• fix: improve limit option validation (#​698)
  • Invalid limit values (e.g. unparseable strings or NaN) now throw instead of being silently ignored, which previously disabled size limit enforcement
  • null and undefined fall back to the default 100kb limit

v1.20.5

Compare Source

======

• refactor(json): simplify strict mode error string construction
• fix: extended urlencoded parsing of arrays with >100 elements (#​716)
• deps: qs@~6.15.1

v1.20.4

Compare Source

======

• deps: qs@~6.14.0
• deps: use tilde notation for dependencies
• deps: http-errors@~2.0.1
• deps: raw-body@~2.5.3

v1.20.3

Compare Source

======

• 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)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dpebot]

/gcbrun

[gemini-code-assist]

Code Review

This pull request updates the body-parser dependency from version 1.20.2 to 1.20.6 in both the backend and frontend packages of the Node.js guestbook application, which also updates several transitive dependencies in the lock files. There are no review comments provided, and I have no additional feedback to offer.

[dpebot]

/gcbrun