Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 3.7 LOWEUVD CVSS 3.1 3.7 CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary 3.7 LOWCVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS_V3 Publisher rating LOWFixed by body-parser 1.20.6Fixed by body-parser 2.3.0KEV status unknown

cve-program · CVE-2026-12590

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-42577

Published

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.

Read the publisher's advisory

nvd · CVE-2026-12590

Published

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.

Read the publisher's advisory

osv · GHSA-v422-hmwv-36x6

Published

### 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 [[email protected]](https://github.com/expressjs/body-parser/releases/tag/v2.3.0) and [[email protected]](https://github.com/expressjs/body-parser/releases/tag/v1.20.6) via [#698](https://github.com/expressjs/body-parser/pull/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()`](https://github.com/visionmedia/bytes.js) at startup and reject any configuration where it returns `null` or a non-finite number. ### References - [#698](https://github.com/expressjs/body-parser/pull/698): fix PR - [bytes.js](https://github.com/visionmedia/bytes.js): limit parser

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-12590

Published

body-parser

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "body-parser",
                    "product": "body-parser",
                    "defaultStatus": "unaffected",
                    "versions": [
                        {
                            "versionType": "semver",
                            "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"
                        }
                    ],
                    "packageURL": "pkg:npm/body-parser"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-42577

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 9, 2026, 10:21:10 AM

dateUpdated: Jul 9, 2026, 12:06:01 PM

2 related source bulletins · separate from aliases

NCSC-2026-0375: Kwetsbaarheden verholpen in Oracle Communications

CVE-2026-9563 · CVE-2026-12590 · CVE-2026-13006 · CVE-2026-13758 · CVE-2026-17544 · CVE-2026-19880 · CVE-2026-34477 · CVE-2026-39822 · CVE-2026-41239 · CVE-2026-41989 · CVE-2026-44024 · CVE-2026-48998 · CVE-2026-49284 · CVE-2026-49844 · CVE-2026-50734 · CVE-2026-54518 · CVE-2026-55952 · CVE-2026-57220 · CVE-2026-58520 · CVE-2026-59943 · CVE-2026-61109 · CVE-2026-63308 · CVE-2026-64849 · CVE-2026-66299 · CVE-2026-67355 · CVE-2026-71290 · CVE-2026-73194 · CVE-2026-73508 · CVE-2026-83417 · CVE-2026-83418 · CVE-2026-83419

WID-SEC-W-2026-3403: Oracle Communications: Mehrere Schwachstellen

CVE-2026-12590 · CVE-2026-13006 · CVE-2026-13758 · CVE-2026-17544 · CVE-2026-19880 · CVE-2026-34477 · CVE-2026-39822 · CVE-2026-41239 · CVE-2026-41989 · CVE-2026-44024 · CVE-2026-48998 · CVE-2026-49284 · CVE-2026-49844 · CVE-2026-50734 · CVE-2026-54518 · CVE-2026-55952 · CVE-2026-57220 · CVE-2026-58520 · CVE-2026-59943 · CVE-2026-61109 · CVE-2026-63308 · CVE-2026-64849 · CVE-2026-66299 · CVE-2026-67355 · CVE-2026-71290 · CVE-2026-73194 · CVE-2026-73508 · CVE-2026-83417 · CVE-2026-83418 · CVE-2026-83419 · CVE-2026-9563

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-12590

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-770

Original publisher date fields

published: 2026-07-09T11:16:24.670

lastModified: 2026-07-10T02:45:02.800

1 source CPE criteria · context only
  • cpe:2.3:a:openjsf:body-parser:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-v422-hmwv-36x6

Published

body-parser

npm

SEMVER · introduced 0 → fixed 1.20.6

body-parser

npm

SEMVER · introduced 2.0.0 → fixed 2.3.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 07:54 UTC · 270 of 275 readable · 255 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current