CVE-2026-12590
body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
Description
Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the 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. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number.
INFO
Published Date :
July 9, 2026, 11:16 a.m.
Last Modified :
July 9, 2026, 1:16 p.m.
Remotely Exploit :
No
Source :
ce714d77-add3-4f53-aff5-83d477b104bb
Affected Products
The following products are affected by CVE-2026-12590
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | LOW | ce714d77-add3-4f53-aff5-83d477b104bb |
Solution
- Update body-parser to version 1.20.6 or 2.3.0.
- Validate limit value before passing to body-parser.
- Reject configurations with invalid limit values.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-12590.
| URL | Resource |
|---|---|
| https://cna.openjsf.org/security-advisories.html | |
| https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-12590 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-12590
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-12590 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-12590 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jul. 09, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-12590', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-07-09T12:05:36.853756Z'} -
New CVE Received by ce714d77-add3-4f53-aff5-83d477b104bb
Jul. 09, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'body-parser', 'product': 'body-parser', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.20.6', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '1.20.6', 'versionType': 'semver'}, {'status': 'affected', 'version': '2.0.0', 'lessThan': '2.3.0', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '2.3.0', 'versionType': 'semver'}], 'packageURL': 'pkg:npm/body-parser', 'defaultStatus': 'unaffected'}] Added Description Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the 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. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number. Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Added CWE CWE-770 Added Reference https://cna.openjsf.org/security-advisories.html Added Reference https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6