Skip to content
Noroxi
CVE-2022-32215· NVD / CVE Program· CNA hackerone

The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding hea

The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Jul 14, 2022
Updated
Jun 17, 2026
EPSS
68.8% · 99th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

47

Plan

Add it to your regular patch cycle.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
21 / 30 · 68.8%

Affected systems

VendorProduct
llhttpllhttp
nodejsnode.js
fedoraprojectfedora
siemenssinec ins
debiandebian linux
stormshieldstormshield management center

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js14.0.0 and later · up to 14.14.0 inclusive
  • nodejs node.js14.15.0 and later · before 14.20.0
  • nodejs node.js16.0.0 and later · up to 16.12.0 inclusive
  • nodejs node.js16.13.0 and later · before 16.16.0
  • nodejs node.js18.0.0 and later · before 18.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • NodeJS Node

    • 4.0 and later · before 4.*affected · semver
    • 5.0 and later · before 5.*affected · semver
    • 6.0 and later · before 6.*affected · semver
    • 7.0 and later · before 7.*affected · semver
    • 8.0 and later · before 8.*affected · semver
    • 9.0 and later · before 9.*affected · semver
    • 10.0 and later · before 10.*affected · semver
    • 11.0 and later · before 11.*affected · semver
    • 12.0 and later · before 12.*affected · semver
    • 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:14.20.0-2.module_el8.6.0+3261+490666b31:14.20.0-2.module_el8.6.0+3261+490666b3
AlmaLinux:8nodejs-develbefore 1:14.20.0-2.module_el8.6.0+3261+490666b31:14.20.0-2.module_el8.6.0+3261+490666b3
AlmaLinux:8nodejs-docsbefore 1:14.20.0-2.module_el8.6.0+3261+490666b31:14.20.0-2.module_el8.6.0+3261+490666b3
AlmaLinux:8nodejs-full-i18nbefore 1:14.20.0-2.module_el8.6.0+3261+490666b31:14.20.0-2.module_el8.6.0+3261+490666b3
AlmaLinux:8nodejs-nodemonbefore 2.0.19-2.module_el8.6.0+3261+490666b32.0.19-2.module_el8.6.0+3261+490666b3
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.5.0+2618+8d46dafd23-3.module_el8.5.0+2618+8d46dafd
AlmaLinux:8npmbefore 1:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b31:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b3
AlmaLinux:9nodejsbefore 1:16.16.0-1.el9_01:16.16.0-1.el9_0
AlmaLinux:9nodejs-docsbefore 1:16.16.0-1.el9_01:16.16.0-1.el9_0
AlmaLinux:9nodejs-full-i18nbefore 1:16.16.0-1.el9_01:16.16.0-1.el9_0
AlmaLinux:9nodejs-libsbefore 1:16.16.0-1.el9_01:16.16.0-1.el9_0
AlmaLinux:9nodejs-nodemonbefore 2.0.19-1.el9_02.0.19-1.el9_0
AlmaLinux:9npmbefore 1:8.11.0-1.16.16.0.1.el9_01:8.11.0-1.16.16.0.1.el9_0
Alpine:v3.13nodejsbefore 14.20.1-r014.20.1-r0
Alpine:v3.15nodejsbefore 16.17.1-r016.17.1-r0
Debian:11nodejsbefore 12.22.12~dfsg-1~deb11u312.22.12~dfsg-1~deb11u3
Debian:12nodejsbefore 18.6.0+dfsg-318.6.0+dfsg-3
openSUSE:Tumbleweednodejs16before 16.17.1-1.116.17.1-1.1
openSUSE:Tumbleweednodejs18before 18.10.0-1.118.10.0-1.1
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:16.16.0-3.module+el8.6.0+16248+76b0e1851:16.16.0-3.module+el8.6.0+16248+76b0e185
Red Hat:enterprise_linux:8::appstreamnodejsbefore 1:14.20.0-2.module+el8.6.0+16231+7c1b33d91:14.20.0-2.module+el8.6.0+16231+7c1b33d9
Red Hat:enterprise_linux:8::appstreamnodejs-debuginfobefore 1:14.20.0-2.module+el8.6.0+16231+7c1b33d91:14.20.0-2.module+el8.6.0+16231+7c1b33d9
Red Hat:enterprise_linux:8::appstreamnodejs-debuginfobefore 1:16.16.0-3.module+el8.6.0+16248+76b0e1851:16.16.0-3.module+el8.6.0+16248+76b0e185
Red Hat:enterprise_linux:8::appstreamnodejs-debugsourcebefore 1:16.16.0-3.module+el8.6.0+16248+76b0e1851:16.16.0-3.module+el8.6.0+16248+76b0e185

+67

Other highest-scoring records for the same primary product.

  • CVE-2022-32214The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP re
    51Plan
  • CVE-2022-32213The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding he
    39Monitor
  • CVE-2022-35256The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF.
    27Monitor
  • CVE-2021-22959The parser in accepts requests with a space (SP) right after the header name before the colon.
    27Monitor
  • CVE-2021-22960The parse function in llhttp < 2.1.4 and < 6.0.6.
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NodeJS Node10.*Vendor (CNA)
NodeJS Node11.*Vendor (CNA)
NodeJS Node12.*Vendor (CNA)
NodeJS Node13.*Vendor (CNA)
NodeJS Node14.20.1Vendor (CNA)
NodeJS Node15.*Vendor (CNA)
NodeJS Node16.17.1Vendor (CNA)
NodeJS Node17.*Vendor (CNA)
NodeJS Node18.9.1Vendor (CNA)
NodeJS Node4.*Vendor (CNA)
NodeJS Node5.*Vendor (CNA)
NodeJS Node6.*Vendor (CNA)
NodeJS Node7.*Vendor (CNA)
NodeJS Node8.*Vendor (CNA)
NodeJS Node9.*Vendor (CNA)
almalinux:nodejs1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-libs1:16.16.0-1.el9_0 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon2.0.19-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging23-3.module_el8.5.0+2618+8d46dafd · AlmaLinux:8Package registry (OSV)
almalinux:npm1:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b3 · AlmaLinux:8Package registry (OSV)
alpine:nodejs14.20.1-r0 · Alpine:v3.13Package registry (OSV)
debian:nodejs18.6.0+dfsg-3 · Debian:12Package registry (OSV)
opensuse:nodejs1010.24.1-150000.1.47.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs1212.22.12-150200.4.35.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs1414.20.0-150200.15.34.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs1616.16.0-150400.3.3.2 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:nodejs1818.13.0-150400.9.3.1 · openSUSE:Leap 15.4Package registry (OSV)

+24

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records