The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2023-30589
PublishedThe llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
- Source published
- 30 Jun 2023 23:39:59 UTC
- Source modified
- 8 Oct 2026 21:13:51 UTC
- Observed 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
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
euvd · EUVD-2023-2033
PublishedThe llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
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: Jun 30, 2023, 11:39:59 PM
dateUpdated: Oct 8, 2026, 9:13:51 PM
23 related source bulletins · separate from aliases
RHSA-2023:4536: Red Hat Security Advisory: nodejs:18 security, bug fix, and enhancement update
CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
SUSE-SU-2023:2669-1: Security update for nodejs18
CVE-2022-25881 · CVE-2023-30581 · CVE-2023-30585 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32067
msrc_CVE-2023-30589: The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3 only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16 v18 and v20
CVE-2023-30589
SUSE-SU-2023:2663-1: Security update for nodejs16
CVE-2023-30581 · CVE-2023-30585 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32067
RHSA-2023:4330: Red Hat Security Advisory: nodejs:18 security, bug fix, and enhancement update
CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
SUSE-SU-2023:3306-1: Security update for nodejs14
CVE-2023-30581 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-32002 · CVE-2023-32006 · CVE-2023-32559
RHSA-2023:4537: Red Hat Security Advisory: nodejs:16 security, bug fix, and enhancement update
CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
RHSA-2023:4331: Red Hat Security Advisory: nodejs security, bug fix, and enhancement update
CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
SUSE-SU-2023:2655-1: Security update for nodejs16
CVE-2023-30581 · CVE-2023-30585 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32067
openSUSE-SU-2024:13564-1: python310-httptools-0.6.1-1.1 on GA media
CVE-2023-30589
openSUSE-SU-2026:12009-1: python313-httptools-0.8.0-1.3 on GA media
CVE-2023-30589
SUSE-SU-2023:3408-1: Security update for nodejs14
CVE-2023-30581 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-32002 · CVE-2023-32006 · CVE-2023-32559
RHSA-2023:5533: Red Hat Security Advisory: nodejs security, bug fix, and enhancement update
CVE-2022-4904 · CVE-2022-25881 · CVE-2023-23920 · CVE-2023-23936 · CVE-2023-24807 · CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-32002 · CVE-2023-32006 · CVE-2023-32559
WID-SEC-W-2023-2917: Xerox FreeFlow Print Server: Mehrere Schwachstellen
CVE-2017-5715 · CVE-2018-3639 · CVE-2021-44917 · CVE-2021-46784 · CVE-2022-31008 · CVE-2022-32206 · CVE-2022-32221 · CVE-2022-3924 · CVE-2022-41409 · CVE-2022-48337 · CVE-2022-48338 · CVE-2022-48339 · CVE-2022-4899 · CVE-2023-0049 · CVE-2023-0051 · CVE-2023-0054 · CVE-2023-0288 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0512 · CVE-2023-0666 · CVE-2023-0668 · CVE-2023-1127 · CVE-2023-1170 · CVE-2023-1175 · CVE-2023-1393 · CVE-2023-1906 · CVE-2023-1981 · CVE-2023-2004 · CVE-2023-22025 · CVE-2023-22043 · CVE-2023-22067 · CVE-2023-22081 · CVE-2023-22128 · CVE-2023-22129 · CVE-2023-23914 · CVE-2023-23915 · CVE-2023-23916 · CVE-2023-24329 · CVE-2023-24805 · CVE-2023-25193 · CVE-2023-2650 · CVE-2023-27985 · CVE-2023-27986 · CVE-2023-2828 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28450 · CVE-2023-2854 · CVE-2023-2855 · CVE-2023-2857 · CVE-2023-2858 · CVE-2023-2879 · CVE-2023-28879 · CVE-2023-2911 · CVE-2023-29402 · CVE-2023-29403 · CVE-2023-29404 · CVE-2023-29405 · CVE-2023-29406 · CVE-2023-29409 · CVE-2023-29491 · CVE-2023-29499 · CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31122 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-3138 · CVE-2023-31484 · CVE-2023-31486 · CVE-2023-3195 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32067 · CVE-2023-3247 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-32573 · CVE-2023-32611 · CVE-2023-32636 · CVE-2023-32643 · CVE-2023-32665 · CVE-2023-32681 · CVE-2023-32762 · CVE-2023-32763 · CVE-2023-34241 · CVE-2023-34969 · CVE-2023-36053 · CVE-2023-36191 · CVE-2023-3666 · CVE-2023-36664 · CVE-2023-37201 · CVE-2023-37202 · CVE-2023-37207 · CVE-2023-37208 · CVE-2023-37211 · CVE-2023-3823 · CVE-2023-3824 · CVE-2023-38403 · CVE-2023-4045 · CVE-2023-4046 · CVE-2023-4047 · CVE-2023-40477 · CVE-2023-4048 · CVE-2023-4049 · CVE-2023-4050 · CVE-2023-4054 · CVE-2023-4055 · CVE-2023-4056 · CVE-2023-41080 · CVE-2023-41081 · CVE-2023-43622 · CVE-2023-4504 · CVE-2023-4573 · CVE-2023-4574 · CVE-2023-4575 · CVE-2023-4576 · CVE-2023-45802 · CVE-2023-4581 · CVE-2023-4584
WID-SEC-W-2023-1523: Node.js: Mehrere Schwachstellen
CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
ICSA-24-046-15: Siemens SINEC NMS
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-1255 · CVE-2023-2454 · CVE-2023-2455 · CVE-2023-2650 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-25690 · CVE-2023-27522 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28709 · CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32067 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-34035 · CVE-2023-35945 · CVE-2023-38039 · CVE-2023-38199 · CVE-2023-38545 · CVE-2023-38546 · CVE-2023-39417 · CVE-2023-39418 · CVE-2023-41080 · CVE-2023-46120 · CVE-2024-23810 · CVE-2024-23811 · CVE-2024-23812
SSA-943925: SSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1
CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-1255 · CVE-2023-2454 · CVE-2023-2455 · CVE-2023-2650 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-25690 · CVE-2023-27522 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28709 · CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32067 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-34035 · CVE-2023-35945 · CVE-2023-38039 · CVE-2023-38199 · CVE-2023-38545 · CVE-2023-38546 · CVE-2023-39417 · CVE-2023-39418 · CVE-2023-41080 · CVE-2023-46120 · CVE-2024-23810 · CVE-2024-23811 · CVE-2024-23812
WID-SEC-W-2023-2692: Oracle Java SE: Mehrere Schwachstellen
CVE-2023-22025 · CVE-2023-22067 · CVE-2023-22081 · CVE-2023-22091 · CVE-2023-30589
SUSE-SU-2023:3455-1: Security update for nodejs12
CVE-2023-23918 · CVE-2023-30581 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-32002 · CVE-2023-32006 · CVE-2023-32559
SUSE-SU-2023:2861-1: Security update for nodejs16
CVE-2023-30581 · CVE-2023-30585 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32067
openSUSE-SU-2024:13021-1: corepack20-20.3.1-1.1 on GA media
CVE-2023-30581 · CVE-2023-30582 · CVE-2023-30583 · CVE-2023-30584 · CVE-2023-30585 · CVE-2023-30586 · CVE-2023-30587 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590
RHSA-2023:5361: Red Hat Security Advisory: nodejs:16 security, bug fix, and enhancement update
CVE-2022-25883 · CVE-2023-30581 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-32002 · CVE-2023-32006 · CVE-2023-32559
SUSE-SU-2023:2662-1: Security update for nodejs18
CVE-2022-25881 · CVE-2023-30581 · CVE-2023-30585 · CVE-2023-30588 · CVE-2023-30589 · CVE-2023-30590 · CVE-2023-31124 · CVE-2023-31130 · CVE-2023-31147 · CVE-2023-32067
- Source published
- Jun 30, 2023, 11:39:59 PM (timezone not stated)
- Source modified
- Oct 8, 2026, 9:13:51 PM (timezone not stated)
- Observed here
- 10 Nov 2026 01:25:06 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
nvd · CVE-2023-30589
PublishedThe llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
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: NVD-CWE-Other
Original publisher date fields
published: 2023-07-01T00:15:10.293
lastModified: 2026-10-08T22:17:24.087
3 source CPE criteria · context only
- cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
- cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
- cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 1 Jul 2023 00:15:10 UTC
- Source modified
- 8 Oct 2026 22:17:24 UTC
- Observed here
- 24 Oct 2026 22:17:10 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
osv · GHSA-cggh-pq45-6h9x
PublishedThe llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
- Source published
- 1 Jul 2023 00:30:46 UTC
- Source modified
- 10 Sep 2026 03:49:57 UTC
- Observed 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
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Publisher rating · HIGH