Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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 CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2022-32214

Published

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 CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

Source published
14 Jul 2022 00:00:00 UTC
Source modified
30 Apr 2025 22:24:43 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2022-6393

Published

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 CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 14, 2022, 12:00:00 AM

dateUpdated: Apr 30, 2025, 10:24:43 PM

19 related source bulletins · separate from aliases

RHSA-2022:6448: Red Hat Security Advisory: nodejs:14 security and bug fix update

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-33987

WID-SEC-W-2022-1461: IBM Spectrum Protect: Mehrere Schwachstellen

CVE-2018-25032 · CVE-2021-22946 · CVE-2021-22947 · CVE-2021-3759 · CVE-2021-42550 · CVE-2022-1292 · CVE-2022-1705 · CVE-2022-2068 · CVE-2022-2097 · CVE-2022-22389 · CVE-2022-22390 · CVE-2022-22476 · CVE-2022-22576 · CVE-2022-23772 · CVE-2022-23773 · CVE-2022-23806 · CVE-2022-24675 · CVE-2022-27774 · CVE-2022-27776 · CVE-2022-27782 · CVE-2022-29361 · CVE-2022-29526 · CVE-2022-29804 · CVE-2022-30580 · CVE-2022-30629 · CVE-2022-30631 · CVE-2022-30633 · CVE-2022-30634 · CVE-2022-31028 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-32222 · CVE-2022-32223 · CVE-2022-33987 · CVE-2022-35919 · CVE-2022-40234 · CVE-2022-40608

SUSE-SU-2022:2491-1: Security update for nodejs16

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

RHSA-2022:6389: Red Hat Security Advisory: rh-nodejs14-nodejs and rh-nodejs14-nodejs-nodemon security and bug fix update

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-33987

WID-SEC-W-2022-0621: Node.js: Mehrere Schwachstellen ermöglichen Codeausführung

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-32222 · CVE-2022-32223

SUSE-SU-2022:2855-1: Security update for nodejs10

CVE-2021-22930 · CVE-2021-22940 · CVE-2021-22959 · CVE-2021-22960 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

SUSE-SU-2022:2417-1: Security update for nodejs12

CVE-2022-2097 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

SUSE-SU-2022:2551-1: Security update for nodejs16

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

SUSE-SU-2023:0419-1: Security update for nodejs18

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-35255 · CVE-2022-35256 · CVE-2022-43548

SUSE-SU-2022:2430-1: Security update for nodejs12

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

SUSE-SU-2022:2425-1: Security update for nodejs14

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

RHSA-2022:6595: Red Hat Security Advisory: nodejs and nodejs-nodemon security and bug fix update

CVE-2020-7788 · CVE-2020-28469 · CVE-2021-3807 · CVE-2021-33502 · CVE-2022-29244 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-33987

WID-SEC-W-2022-1375: JFrog Artifactory: Mehrere Schwachstellen

CVE-2013-4517 · CVE-2013-7285 · CVE-2014-0107 · CVE-2014-0114 · CVE-2014-3577 · CVE-2014-3623 · CVE-2015-0227 · CVE-2015-2575 · CVE-2015-3253 · CVE-2015-4852 · CVE-2015-7940 · CVE-2016-10750 · CVE-2016-3092 · CVE-2016-3674 · CVE-2016-6501 · CVE-2016-8735 · CVE-2016-8745 · CVE-2017-1000487 · CVE-2017-15095 · CVE-2017-17485 · CVE-2017-18214 · CVE-2017-18640 · CVE-2017-7525 · CVE-2017-7657 · CVE-2017-7957 · CVE-2017-9506 · CVE-2018-1000206 · CVE-2018-9116 · CVE-2019-10219 · CVE-2019-12402 · CVE-2019-17359 · CVE-2019-17571 · CVE-2019-20104 · CVE-2020-11996 · CVE-2020-13934 · CVE-2020-13935 · CVE-2020-13949 · CVE-2020-14340 · CVE-2020-15586 · CVE-2020-1745 · CVE-2020-17521 · CVE-2020-25649 · CVE-2020-28500 · CVE-2020-29582 · CVE-2020-36518 · CVE-2020-7226 · CVE-2020-7692 · CVE-2020-8203 · CVE-2021-13936 · CVE-2021-21290 · CVE-2021-22060 · CVE-2021-22112 · CVE-2021-22119 · CVE-2021-22147 · CVE-2021-22148 · CVE-2021-22149 · CVE-2021-22573 · CVE-2021-23337 · CVE-2021-25122 · CVE-2021-26291 · CVE-2021-27568 · CVE-2021-29505 · CVE-2021-30129 · CVE-2021-33037 · CVE-2021-35550 · CVE-2021-35556 · CVE-2021-35560 · CVE-2021-35561 · CVE-2021-35564 · CVE-2021-35565 · CVE-2021-35567 · CVE-2021-35578 · CVE-2021-35586 · CVE-2021-35588 · CVE-2021-35603 · CVE-2021-36374 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-38561 · CVE-2021-3859 · CVE-2021-41090 · CVE-2021-41091 · CVE-2021-42340 · CVE-2021-42550 · CVE-2021-43797 · CVE-2022-0536 · CVE-2022-22963 · CVE-2022-23632 · CVE-2022-23648 · CVE-2022-23806 · CVE-2022-24769 · CVE-2022-24823 · CVE-2022-27191 · CVE-2022-29153 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-32223

RHSA-2022:6985: Red Hat Security Advisory: nodejs:14 security and bug fix update

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-33987

msrc_CVE-2022-32214: 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 CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

CVE-2022-32214

SUSE-SU-2023:0408-1: Security update for nodejs18

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-35255 · CVE-2022-35256 · CVE-2022-43548

RHSA-2022:6449: Red Hat Security Advisory: nodejs:16 security and bug fix update

CVE-2021-3807 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-33987

SUSE-SU-2022:2416-1: Security update for nodejs14

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

SUSE-SU-2022:2415-1: Security update for nodejs16

CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215

Source published
Jul 14, 2022, 12:00:00 AM (timezone not stated)
Source modified
Apr 30, 2025, 10:24:43 PM (timezone not stated)
Saved here
18 Nov 2026 03:29:33 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

nvd · CVE-2022-32214

Published

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 CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-444

Original publisher date fields

published: 2022-07-14T15:15:08.337

lastModified: 2026-06-17T04:46:53.167

5 source CPE criteria · context only
  • cpe:2.3:a:llhttp:llhttp:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
  • cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:stormshield:stormshield_management_center:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
14 Jul 2022 15:15:08 UTC
Source modified
17 Jun 2026 04:46:53 UTC
Saved here
24 Oct 2026 20:17:30 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Primary · 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

osv · GHSA-q5vx-44v4-gch4

Published

The llhttp parser in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. The LF character (without CR) is sufficient to delimit HTTP header fields in the lihttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This can lead to HTTP Request Smuggling (HRS).

Source published
15 Jul 2022 00:00:18 UTC
Source modified
10 Sep 2026 03:49:55 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · CRITICAL

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 03:46 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current