CVE-2025-23167
mediumpriority · track · 10EPSS 0.005 · 43 %ileexploit · PoCDEEURUUSEPSS · scored 2026-10-26
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (1)
Public proof-of-concept and weaponised exploit code.
affected products (42)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-1055Node.js: Mehrere SchwachstellenDeutsch2025-05-14csaf · cert_bundDE
Ein lokaler Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen oder Sicherheitsvorkehrungen zu umgehen.
- BIT-node-2025-231672025-05-21vendor · osvUS
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.
- BIT-node-min-2025-231672025-05-21vendor · osvUS
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.
also known as (6)
Other names and identifiers for this entity.
- CNNVD-202505-2718cnnvd
- EUVD-2025-27706enisa_euvd
- BDU:2025-10618fstec_bdu
- GHSA-hchw-qwx7-4w4cenisa_euvd
- BIT-node-2025-23167osv
- BIT-node-min-2025-23167osv
sources
Which sources assert this record, and when.
references (5)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2025-23167cnnvd
- https://nodejs.org/en/blog/vulnerability/may-2025-security-releasescnnvd
- https://nodejs.org/en/downloadPatchcnnvd
- https://nodejs.org/en/blog/vulnerability/may-2025-security-releasesenisa_euvd
- https://nodejs.org/en/blog/vulnerability/may-2025-security-releasesnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan