PatchTheCVECVE-2022-32213: The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and
62
This week
MEDIUM 6.5REMOTEWATCHLISTUPGRADEUPGRADEMITIGATE
CVE-2022-32213 is a medium-severity flaw (CVSS 6.5) affecting llhttp, node.js, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The 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 headers and can lead to HTTP Request Smuggling (HRS).
Why this priority
- EPSS top 1%: very likely to be exploited
- Public exploit reference
- Remotely exploitable, no login, no user action
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 44.8% (top 1%) |
| CISA exploited list | No |
| Weakness | CWE-444 |
| Published | 2022-07-14 |
| Last modified | 2026-06-17 |
Publisher (CNA): HackerOne · Vendor: debian · fedoraproject · llhttp · nodejs · siemens · stormshield
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
llhttp llhttp UPGRADE
Affected: < 2.1.5 · >= 6.0.0 and < 6.0.7
Fixed in: 2.1.5, 6.0.7
Safe to downgrade to: a release before 6.0.0
1. Check installed version
npm ls llhttp
2. UPGRADE to 2.1.5
npm install llhttp@">=2.1.5"
3. If no update is available yet, DOWNGRADE to a release before 6.0.0
npm view llhttp versions
npm install llhttp@"<6.0.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
nodejs node.js UPGRADE
Affected: >= 14.0.0 and <= 14.14.0 · >= 14.15.0 and < 14.20.1 · >= 16.0.0 and <= 16.12.0 · >= 16.13.0 and < 16.17.1 · >= 18.0.0 and < 18.9.1
Fixed in: 14.20.1, 16.17.1, 18.9.1
Safe to downgrade to: a release before 14.0.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to 14.20.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade node.js
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade node.js
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 14.0.0 (Debian / Ubuntu)
apt-cache madison node.js
sudo apt install node.js=<VERSION_BEFORE_14.0.0>
sudo apt-mark hold node.js
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js
sudo dnf downgrade node.js-<VERSION_BEFORE_14.0.0>
sudo dnf versionlock add node.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fedoraproject fedora MITIGATE
Affected: 35 · 36 · 37
Fixed in: no fixed release known
Safe to downgrade to: a release before 35
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
siemens sinec ins DOWNGRADE
Affected: 1.0 · 1.0 sp1 · 1.0 sp2
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy sinec-ins || rpm -q sinec-ins || sinec-ins --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison sinec-ins
sudo apt install sinec-ins=<VERSION_BEFORE_1.0>
sudo apt-mark hold sinec-ins
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sinec-ins
sudo dnf downgrade sinec-ins-<VERSION_BEFORE_1.0>
sudo dnf versionlock add sinec-ins
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
debian debian linux MITIGATE
Affected: 11.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 11.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
stormshield stormshield management center UPGRADE
Affected: < 3.3.2
Fixed in: 3.3.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy stormshield-management-center || rpm -q stormshield-management-center || stormshield-management-center --version
2. UPGRADE to 3.3.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade stormshield-management-center
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade stormshield-management-center
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-32213?
llhttp: upgrade to 2.1.5, 6.0.7; node.js: upgrade to 14.20.1, 16.17.1, 18.9.1; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-32213 being exploited?
CVE-2022-32213 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-32213 affect?
CVE-2022-32213 affects llhttp, node.js, fedora. Severity is medium (CVSS 6.5). The 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 headers and can lead to HTTP Request Smuggling (HRS).
How urgent is CVE-2022-32213?
Priority 62/100. EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist
Software pages
Node.js vulnerabilities · Debian vulnerabilities · Siemens vulnerabilities
Related CVEs
- CVE-2022-35256 MEDIUM 6.5 UPGRADE UPGRADE The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not term
- CVE-2022-32215 MEDIUM 6.5 UPGRADE UPGRADE The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle mu
- CVE-2022-32214 MEDIUM 6.5 UPGRADE UPGRADE The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CR
- CVE-2021-22960 MEDIUM 6.5 UPGRADE DOWNGRADE The parse function in llhttp < 2.1.4 and < 6.0.6
- CVE-2021-22959 MEDIUM 6.5 UPGRADE DOWNGRADE The parser in accepts requests with a space (SP) right after the header name before the colon