Skip to content
Noroxi
CVE-2024-27982· NVD / CVE Program· CNA hackerone

The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to

The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first.

MediumCVSS 6.5 · v3.0—No exploit Fix available
Published
May 7, 2024
Updated
Jun 17, 2026
EPSS
1.2% · 66th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · hackerone
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
nodejsnode.js

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • NodeJS Node

    • 4.0 and later · before 4.*affected · semver
    • 5.0 and later · before 5.*affected · semver
    • 6.0 and later · before 6.*affected · semver
    • 7.0 and later · before 7.*affected · semver
    • 8.0 and later · before 8.*affected · semver
    • 9.0 and later · before 9.*affected · semver
    • 10.0 and later · before 10.*affected · semver
    • 11.0 and later · before 11.*affected · semver
    • 12.0 and later · before 12.*affected · semver
    • 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejsbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-develbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-develbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-docsbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-docsbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-full-i18nbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-full-i18nbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.8.0+3613+1ed8c91d3.0.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.9.0+3731+490e3ce53.0.1-1.module_el8.9.0+3731+490e3ce5
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8npmbefore 1:10.5.0-1.18.20.2.1.module_el8.9.0+3828+c9fa96441:10.5.0-1.18.20.2.1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8npmbefore 1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e
AlmaLinux:9nodejsbefore 1:16.20.2-8.el9_41:16.20.2-8.el9_4
AlmaLinux:9nodejsbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejsbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejs-develbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejs-develbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejs-docsbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejs-docsbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejs-docsbefore 1:16.20.2-8.el9_41:16.20.2-8.el9_4

+96

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 f
    58Plan
  • CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
    35Monitor
  • CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a
    32Monitor
  • CVE-2024-36138Bypass incomplete fix of CVE-2024-27980, that arises from improper handling of batch files with all possible extensions on Windows via child
    32Monitor
  • CVE-2026-56848A flaw in Node.js HTTP/2 handling allows `nghttp2_session_mem_send()` to be called re-entrantly while `nghttp2_session_mem_recv()` is execut
    30Monitor
  • CVE-2026-56846A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion.
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NodeJS Node10.*Vendor (CNA)
NodeJS Node11.*Vendor (CNA)
NodeJS Node12.*Vendor (CNA)
NodeJS Node13.*Vendor (CNA)
NodeJS Node14.*Vendor (CNA)
NodeJS Node15.*Vendor (CNA)
NodeJS Node16.*Vendor (CNA)
NodeJS Node17.*Vendor (CNA)
NodeJS Node18.20.1Vendor (CNA)
NodeJS Node19.*Vendor (CNA)
NodeJS Node20.12.1Vendor (CNA)
NodeJS Node21.7.2Vendor (CNA)
NodeJS Node4.*Vendor (CNA)
NodeJS Node5.*Vendor (CNA)
NodeJS Node6.*Vendor (CNA)
NodeJS Node7.*Vendor (CNA)
NodeJS Node8.*Vendor (CNA)
NodeJS Node9.*Vendor (CNA)
almalinux:nodejs1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-libs1:16.20.2-8.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el8.9.0+3731+490e3ce5 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging2021.06-4.module_el8.9.0+3684+11b9e959 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el8.9.0+3684+11b9e959 · AlmaLinux:8Package registry (OSV)
almalinux:npm1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
alpine:nodejs18.20.1-r0 · Alpine:v3.17Package registry (OSV)
debian:nodejs18.20.4+dfsg-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:nodejs1818.20.1-150400.9.21.3 · openSUSE:Leap 15.5Package registry (OSV)

+23

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-23167376 days apartA flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records