Node.js up to 20.19.1 HTTP Parser request smuggling

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.8$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Node.js up to 20.19.1. Affected by this vulnerability is an unknown functionality of the component HTTP Parser. Performing a manipulation results in request smuggling. This vulnerability is reported as CVE-2025-23167. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Node.js up to 20.19.1. It has been classified as critical. This affects some unknown functionality of the component HTTP Parser. The manipulation with an unknown input leads to a request smuggling vulnerability. CWE is classifying the issue as CWE-444. The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A 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`. This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests. The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination. Impact: * This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.

It is possible to read the advisory at nodejs.org. This vulnerability is uniquely identified as CVE-2025-23167 since 01/12/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 236766 (Node.js 20.x < 20.19.2 / 22.x < 22.15.1 / 22.x < 22.15.1 / 23.x < 23.11.1 / 24.x < 24.0.2 Multiple Vulnerabilities (Wednesday, May 14, 2025 Security Releases).), which helps to determine the existence of the flaw in a target environment.

Upgrading eliminates this vulnerability. The upgrade is hosted for download at nodejs.org.

The vulnerability is also documented in the databases at Tenable (236766) and CERT Bund (WID-SEC-2025-1055). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Red Hat Enterprise Linux
  • Fedora Linux
  • SUSE Linux
  • Oracle Linux
  • Open Source Arch Linux
  • IBM Business Automation Workflow
  • Dell Data Protection Advisor
  • IBM App Connect Enterprise
  • Hitachi Ops Center
  • Open Source Node.js

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.8

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (hackerone): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Request smuggling
CWE: CWE-444
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 236766
Nessus Name: Node.js 20.x < 20.19.2 / 22.x < 22.15.1 / 22.x < 22.15.1 / 23.x < 23.11.1 / 24.x < 24.0.2 Multiple Vulnerabilities (Wednesday, May 14, 2025 Security Releases).

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: nodejs.org

Timelineinfo

01/12/2025 🔍
05/19/2025 +126 days 🔍
05/19/2025 +0 days 🔍
10/30/2025 +164 days 🔍

Sourcesinfo

Advisory: nodejs.org
Status: Confirmed

CVE: CVE-2025-23167 (🔍)
GCVE (CVE): GCVE-0-2025-23167
GCVE (VulDB): GCVE-100-309507
CERT Bund: WID-SEC-2025-1055 - Node.js: Mehrere Schwachstellen

Entryinfo

Created: 05/19/2025 08:31
Updated: 10/30/2025 09:23
Changes: 05/19/2025 08:31 (63), 05/19/2025 12:20 (2), 08/09/2025 18:43 (7), 09/11/2025 16:45 (1), 10/30/2025 09:23 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!