Disclosure summary
The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. The HTTP specification does not allow for spaces in the `Content-Length` value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for `Content-Length`. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete.
Source-reported weakness categories
CWE-115, CWE-20
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST National Vulnerability Database · NVD-CVE-2018-7159
Open original source · Updated Oct 08, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| nodejs | node.js | * {"versionStartIncluding":"9.0.0","versionEndExcluding":"9.10.0"} |
| nodejs | node.js | * {"versionStartIncluding":"8.9.0","versionEndExcluding":"8.11.0"} |
Original records & references
- NIST NVD record
- CVE Program record
- access.redhat.com — Third Party Advisory
- nodejs.org — Vendor Advisory
- support.f5.com
- access.redhat.com — Third Party Advisory
- nodejs.org — Vendor Advisory
- support.f5.com
PUBLISHED 2018-05-17T10:29:00-04:00
MODIFIED 2026-10-08T18:16:47-04:00
INGESTED 2026-10-10T20:50:18-04:00