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.
CVE-2018-7159
“—” beside the score: it is equal to NVD's CVSS score.
Score 5.3 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation3.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 3.6%
- EPSS %ILE
- 89th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 3.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 17, 2018
Last Modified
October 8, 2026
Advisory Details (3)
Auto-updated Oct 8, 2026Node.js — March 2018 Security Releases
https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/Affected: Red Hat Enterprise Linux 7.
https://access.redhat.com/errata/RHSA-2019:2258Vendor Advisories for CVE-2018-7159(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2018-7159Microsoft Security Response Center (MSRC)Medium
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.
- GHSA-87vg-5pwm-8x6wGitHub Security AdvisoriesMedium
The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header,...
- RHSA-2019:2258Red Hat Product SecurityMedium
Red Hat Security Advisory: http-parser security update
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | http-parser-0:2.7.1-8.el7 | 2019-08-06 | redhat |
| redhat | rh-nodejs8-nodejs-0:8.11.4-1.el7 | 2018-10-18 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(21 across 21 ecosystems)
Alpine:v3.10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 8× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 179 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-22 16:28 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-20 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-18 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-18 10:02 UTCEG score recompute
- 2026-10-17 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-16 16:30 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-15 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-14 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-13 16:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-12 20:08 UTCEG score recompute
- 2026-10-12 16:28 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-12 00:32 UTCEG score recompute
- 2026-10-11 13:41 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-09 20:03 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-08 22:31 UTCVendor advisory
- 2026-10-08 22:31 UTCGHSA enrichmentGHSA-87vg-5pwm-8x6w · GitHub CVSS 5.3
- 2026-10-08 21:35 UTCEG score recompute
- 2026-10-08 21:35 UTCVendor advisory
- 2026-10-08 21:35 UTCGHSA enrichmentGHSA-87vg-5pwm-8x6w · GitHub CVSS 5.3
- 2026-10-08 16:37 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-07 23:42 UTCEPSS rescoreEPSS 3.6% · 89th percentile
Show 70 moreShow fewer
- 2026-10-06 15:12 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-10-05 17:39 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-10-03 14:21 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-10-01 19:44 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-30 14:59 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-30 10:04 UTCEG score recompute
- 2026-09-29 15:12 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-29 04:32 UTCOSV refresh
- 2026-09-28 13:46 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-27 13:40 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-26 15:53 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-23 13:42 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-21 20:27 UTCEPSS rescoreEPSS 3.6% · 89th percentile
- 2026-09-20 20:10 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-19 15:36 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-18 19:22 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-15 03:05 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-11 14:48 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-11 09:32 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-09 09:00 UTCOSV refresh
- 2026-09-06 13:44 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-04 05:02 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-09-01 03:32 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-30 01:18 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-28 21:36 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-27 14:21 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-26 14:42 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-25 13:45 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-24 14:11 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-22 17:37 UTCOSV refresh
- 2026-08-21 23:45 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-20 22:51 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-19 17:00 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-18 13:44 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-17 13:43 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-16 14:52 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-13 21:56 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-12 13:47 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-09 13:43 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-08 16:32 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-07 16:23 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-06 21:34 UTCOSV refresh
- 2026-08-06 13:42 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-04 15:05 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-04 10:33 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-03 10:31 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-02 02:23 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-08-01 04:12 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-30 16:24 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-30 01:27 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-27 14:05 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-25 14:14 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-24 14:14 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-23 14:15 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-23 01:37 UTCEG score recompute
- 2026-07-22 22:17 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-21 13:17 UTCOSV refresh
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 3.6% · 88th percentile
- 2026-07-19 14:28 UTCEPSS rescoreEPSS 3.6% · 88th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.8:nodejs · Alpine:v3.9:nodejs
- CVE-2018-7160EG 8.8EPSS p96HIGH
- CVE-2018-12122NVD 7.5EG 7.8EPSS p99HIGH
- CVE-2018-12121EG 7.5EPSS p96HIGH
- CVE-2018-12115EG 7.5EPSS p95HIGH
- CVE-2018-7167EG 7.5EPSS p94HIGH
- CVE-2018-7161EG 7.5EPSS p94HIGH
- CVE-2018-7158EG 7.5HIGH
- CVE-2018-12123EG 4.3EPSS p91MEDIUM
- CVE-2019-15606EG 9.8EPSS p97CRITICAL
- CVE-2019-15605EG 9.8EPSS p99CRITICAL
Same vendor
5 shownredhat:RHSA-2018:2949 · redhat:RHSA-2019:2258
Same CWE
10 shownCWE-20
Frequently asked(5)
What is CVE-2018-7159?
When was CVE-2018-7159 made public?
Is CVE-2018-7159 actively exploited?
What is the CVSS score of CVE-2018-7159?
How do I remediate CVE-2018-7159?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-7159
Is Your Infrastructure Affected by CVE-2018-7159?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.