CVE-2023-30589

What it is

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

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering.

Exploit odds

3.9% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-07-01 00:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-08 22:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.9% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-07-01 00:15 UTC

Last modified

2026-10-08 22:17 UTC

Exploit probability

3.9% · EPSS, next 30 days

Record status

Modified

Affected

• Nodejs node.js < 16.20.1
• Nodejs node.js < 18.16.1
• Nodejs node.js < 20.3.1
• Fedoraproject Fedora 37
• Fedoraproject Fedora 38

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-30589.md and follow it. Check whether this project is affected by CVE-2023-30589. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge