{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "2.0.0"
                  },
                  {
                    "fixed": "2.4.0"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              },
              {
                "range": [
                  {
                    "introduced": "0"
                  },
                  {
                    "fixed": "1.20.9"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          },
          "events": [
            {
              "introduced": "9e06a79ca94da7c603a03d7deec56a54f8951330"
            },
            {
              "fixed": "b4744d739e1e2e5257f2ddac31eed191aa5152a4"
            },
            {
              "introduced": "0"
            },
            {
              "fixed": "a64f1404e256b3f0e3ce633e081a7593fe482203"
            }
          ],
          "repo": "https://github.com/expressjs/body-parser",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-27r3-jxmh-p828"
  ],
  "database_specific": {
    "cna_assigner": "openjs",
    "cwe_ids": [
      "CWE-248"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/111xxx/CVE-2026-111181.json"
  },
  "details": "body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream 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 matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.",
  "id": "CVE-2026-111181",
  "modified": "2026-10-28T02:30:35.087309020Z",
  "published": "2026-10-22T14:29:56.577Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://cna.openjsf.org/security-advisories.html"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/111xxx/CVE-2026-111181.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111181"
    }
  ],
  "schema_version": "1.9.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body"
}