{"items":[{"id":"NVI-00016050","kind":"vulnerability","title":"body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-v422-hmwv-36x6","CVE-2026-12590"],"plain_summary":"GitHub lists this reviewed advisory for body-parser, body-parser. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-54578522400a88a504fc8b348960b425"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-20T23:23:28.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0f1c86bd6f85f173998d6088a70ea43d"},{"kind":"CVSS","as_of":"2026-07-10T02:45:02.800Z","value":"3.7 LOW (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-54578522400a88a504fc8b348960b425"},{"kind":"CVSS","as_of":"2026-07-10T02:45:02.800Z","value":"5.9 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-54578522400a88a504fc8b348960b425"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0f1c86bd6f85f173998d6088a70ea43d","url":"https://github.com/advisories/GHSA-v422-hmwv-36x6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v422-hmwv-36x6","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T22:35:18.117Z"},{"id":"sr-54578522400a88a504fc8b348960b425","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12590","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-12590","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-07T13:55:30.071Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0f1c86bd6f85f173998d6088a70ea43d"],"technology":"body-parser","known_exclusions":[],"conditions_summary":"### Impact\n\nWhen 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.\n\nThis issue affects applications that pass a programmatically computed or user-configurable value to the `limit` option without validating it first.\n\n### Patches\n\nThis 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`).\n\n### Workarounds\n\nValidate `limit` before passing it to body-parser. For example, parse the value with `bytes.parse()` at startu","public_affected_ranges":["< 1.20.6"]},{"certainty":"source_listed","source_ids":["sr-0f1c86bd6f85f173998d6088a70ea43d"],"technology":"body-parser","known_exclusions":[],"conditions_summary":"### Impact\n\nWhen 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.\n\nThis issue affects applications that pass a programmatically computed or user-configurable value to the `limit` option without validating it first.\n\n### Patches\n\nThis 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`).\n\n### Workarounds\n\nValidate `limit` before passing it to body-parser. For example, parse the value with `bytes.parse()` at startu","public_affected_ranges":[">= 2.0.0, < 2.3.0"]}],"null_published_at":"2026-11-07T18:43:12.111Z","source_updated_at":"2026-07-20T23:23:28.000Z","source_disclosed_at":"2026-07-20T23:23:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-03T22:35:18.117Z"},{"id":"NVI-00016050","kind":"vulnerability","title":"body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v422-hmwv-36x6","CVE-2026-12590"],"plain_summary":"GitHub lists this reviewed advisory for body-parser, body-parser. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0f1c86bd6f85f173998d6088a70ea43d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-20T23:23:28.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0f1c86bd6f85f173998d6088a70ea43d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0f1c86bd6f85f173998d6088a70ea43d","url":"https://github.com/advisories/GHSA-v422-hmwv-36x6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v422-hmwv-36x6","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T22:35:18.117Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0f1c86bd6f85f173998d6088a70ea43d"],"technology":"body-parser","known_exclusions":[],"conditions_summary":"### Impact\n\nWhen 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.\n\nThis issue affects applications that pass a programmatically computed or user-configurable value to the `limit` option without validating it first.\n\n### Patches\n\nThis 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`).\n\n### Workarounds\n\nValidate `limit` before passing it to body-parser. For example, parse the value with `bytes.parse()` at startu","public_affected_ranges":["< 1.20.6"]},{"certainty":"source_listed","source_ids":["sr-0f1c86bd6f85f173998d6088a70ea43d"],"technology":"body-parser","known_exclusions":[],"conditions_summary":"### Impact\n\nWhen 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.\n\nThis issue affects applications that pass a programmatically computed or user-configurable value to the `limit` option without validating it first.\n\n### Patches\n\nThis 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`).\n\n### Workarounds\n\nValidate `limit` before passing it to body-parser. For example, parse the value with `bytes.parse()` at startu","public_affected_ranges":[">= 2.0.0, < 2.3.0"]}],"null_published_at":"2026-11-04T10:04:27.870Z","source_updated_at":"2026-07-20T23:23:28.000Z","source_disclosed_at":"2026-07-20T23:23:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T22:35:18.117Z"}],"next_cursor":null,"snapshot_revision":"42594"}