LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects Node.js HTTP parsing. Certain Transfer-Encoding headers could be interpreted incorrectly, creating HTTP request smuggling risk when Node.js services sit behind proxies, gateways, or load balancers. That can let one request be misread as another by different systems.

Executive priority

Prioritize remediation for public Node.js services and packaged products using affected runtimes. The issue can affect request trust boundaries, but the provided sources do not confirm active exploitation.

Technical view

CVE-2022-32213 is a CWE-444 HTTP Request Smuggling flaw in Node.js llhttp handling of Transfer-Encoding validation. The source bundle identifies affected Node.js versions before 14.20.1, 16.17.1, and 18.9.1 across Node 4 through 18 release lines.

Likely exposure

Most relevant exposure is internet-facing Node.js HTTP services, API backends, or applications behind reverse proxies where parser disagreement can affect routing, authentication, caching, or request boundaries.

Exploitation context

The bundle includes a public HackerOne report, but KEV is false and no provided source states active exploitation. Treat exploitation as plausible for exposed HTTP services, not confirmed in the wild.

Researcher notes

Focus assessment on parser differentials involving Transfer-Encoding between front-end infrastructure and Node.js llhttp. Do not assume all Node deployments are exploitable; exposure depends on HTTP topology and runtime version. No CVSS score is provided in the bundle.

Mitigation direction

  • Upgrade Node.js to 14.20.1, 16.17.1, 18.9.1, or later supported releases.
  • Prioritize externally reachable Node.js HTTP services behind proxies or gateways.
  • Apply relevant downstream vendor updates for Fedora, Debian, and affected Siemens products.
  • Check vendor guidance for environment-specific compensating controls.

Validation and detection

  • Inventory deployed Node.js runtime versions across servers, containers, and build images.
  • Confirm no production service uses Node.js below the fixed release thresholds.
  • Review proxy-to-Node request handling paths for request smuggling exposure.
  • Verify distro or product packages include the vendor security update.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-444: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-32213 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NodeJSNode4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.