CVE-2025-23167
First published: Mon May 19 2025(Updated: )
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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Node.js | <20.x |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-23167?
CVE-2025-23167 is considered a critical severity vulnerability due to its potential to enable request smuggling and bypass access controls.
How do I fix CVE-2025-23167?
To fix CVE-2025-23167, upgrade Node.js to version 20.x or later, where this vulnerability has been resolved.
Which versions of Node.js are affected by CVE-2025-23167?
CVE-2025-23167 affects all Node.js versions prior to and including 20.x.
What kind of attacks can be executed due to CVE-2025-23167?
CVE-2025-23167 allows attackers to perform request smuggling attacks, which can lead to unauthorized request submissions.
How does CVE-2025-23167 affect web applications?
CVE-2025-23167 can compromise web applications by allowing attackers to bypass proxy-based access controls, posing a security risk.
- agent/references
- agent/author
- agent/source
- agent/first-publish-date
- agent/type
- agent/description
- agent/severity
- agent/trending
- agent/guess-ai
- agent/software-canonical-lookup
- agent/tags
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/weakness
- agent/event
- vendor/node.js
- canonical/node.js