How severe is CVE-2022-32213?

CVE-2022-32213 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-32213?

CVE-2022-32213 affects the following packages: llhttp (npm). Ecosystems affected: npm.

How do I fix CVE-2022-32213?

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.

How do I detect CVE-2022-32213 in my npm dependencies?

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.

How do I mitigate CVE-2022-32213 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-32213 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-32213, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-32213?

CVE-2022-32213 has an EPSS (Exploit Prediction Scoring System) score of 44.8%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-32213?

CVE-2022-32213 is classified as CWE-444 (CWE-444). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-32213 published, and has it been updated?

CVE-2022-32213 was published on July 14, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

CVE-2022-32213 — llhttp

CRITICALFix: nodejs/llhttp@18a4afc

CVE-2022-32213 is a critical-severity (CVSS 9.1) CWE-444 vulnerability in llhttp. 1 public exploit or proof-of-concept reference is indexed, 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

Also known asBIT-node-2022-32213BIT-node-min-2022-32213GHSA-5689-v88g-g6rv

Published

Jul 14, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

44.8%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

llhttpnpm

63downloads / week

Description

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`llhttp`	all versions	6.0.7`npm install llhttp@6.0.7`

Affected Products

6 products · 15 configurations

debian linuxdebian

1 version

11.0

fedorafedoraproject

3 versions

353637

Application

llhttpllhttp

≥ 6.0.0 && < 6.0.7

range

Application

node.jsnodejs

≥ 18.0.0 && ≤ 16.12.0

range

Application

sinec inssiemens

1 version

1.0

Application

stormshield management centerstormshield

< 3.3.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module i…

hackerone.comNVDOct 2022

Detection & mitigation playbook

Open-source dependency

Detect
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.

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.

Red HatModerate

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

UbuntuMEDIUM

USN-6491-1Ubuntu

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2022-32213 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2022-32213 — llhttp

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-32213 in your dependencies?