CVE-2022-32213 is a critical-severity (CVSS 9.1) CWE-444 vulnerability in llhttp. 1 public exploit reference exists, so weaponization risk is real. A fix is available for llhttp — see the affected versions and patch details below.
llhttp allows HTTP Request Smuggling via Flawed Parsing of Transfer-Encoding
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-32213 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
llhttpnpmDescription
The llhttp parser in the http module in Node.js v17.x does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).
Impacts:
- All versions of the nodejs 18.x, 16.x, and 14.x releases lines.
- llhttp v6.0.7 and llhttp v2.1.5 contains the fixes that were updated inside Node.js
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | llhttp | all versions | 6.0.7npm install llhttp@6.0.7 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for llhttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update llhttp to 6.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32213 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-32213 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-32213. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | nodejs:14-8060020220804102127.ad008a3a | RHSA-2022:6448 |
| Red Hat Enterprise Linux 8 | nodejs:16-8060020220805104227.ad008a3a | RHSA-2022:6449 |
| Red Hat Enterprise Linux 8.4 Extended Update Support | nodejs:14-8040020220804130254.522a0ee4 | RHSA-2022:6985 |
| Red Hat Enterprise Linux 9 | nodejs-1:16.16.0-1.el9_0 | RHSA-2022:6595 |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | rh-nodejs14-nodejs-0:14.20.0-2.el7 | RHSA-2022:6389 |
Frequently Asked Questions
Is CVE-2022-32213 in your dependencies?
O3 Security finds CVE-2022-32213 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.