CVE-2025-23167: 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`.
Noroxi assessment
Priority: Monitor (action score 26/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: nodejs node 10.*, 11.*, 12.*; azl3 fluent-bit 3.1.9-4 on Azure Linux 3.0 CBL-Mariner Releases; cbl2 fluent-bit 3.0.6-2 on CBL Mariner 2.0 CBL-Mariner Releases.
Low priority for now. Upgrade to nodejs node 10.*, 11.*, 12.*; azl3 fluent-bit 3.1.9-4 on Azure Linux 3.0 CBL-Mariner Releases; cbl2 fluent-bit 3.0.6-2 on CBL Mariner 2.0 CBL-Mariner Releases or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-444
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | node-undici | from 0 | — |
| Debian:14 | node-undici | before 7.15.0+dfsg+~cs3.2.0-1 | 7.15.0+dfsg+~cs3.2.0-1 |
| openSUSE:Leap 15.6 | nodejs20 | before 20.19.2-150600.3.12.1 | 20.19.2-150600.3.12.1 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-nodemon | before 0:3.0.1-1.module+el8.10.0+23139+21ba74c5 | 0:3.0.1-1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-packaging | before 0:2021.06-4.module+el8.10.0+23139+21ba74c5 | 0:2021.06-4.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | nodejs-packaging-bundler | before 0:2021.06-4.module+el8.10.0+23139+21ba74c5 | 0:2021.06-4.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:8::appstream | npm | before 1:10.8.2-1.20.19.2.1.module+el8.10.0+23139+21ba74c5 | 1:10.8.2-1.20.19.2.1.module+el8.10.0+23139+21ba74c5 |
| Red Hat:enterprise_linux:9::appstream | nodejs | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-debuginfo | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-debugsource | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-devel | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-docs | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-full-i18n | before 1:20.19.2-1.module+el9.6.0+23146+be9976bd | 1:20.19.2-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-nodemon | before 0:3.0.1-1.module+el9.6.0+23146+be9976bd | 0:3.0.1-1.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-packaging | before 0:2021.06-4.module+el9.6.0+23146+be9976bd | 0:2021.06-4.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | nodejs-packaging-bundler | before 0:2021.06-4.module+el9.6.0+23146+be9976bd | 0:2021.06-4.module+el9.6.0+23146+be9976bd |
| Red Hat:enterprise_linux:9::appstream | npm | before 1:10.8.2-1.20.19.2.1.module+el9.6.0+23146+be9976bd | 1:10.8.2-1.20.19.2.1.module+el9.6.0+23146+be9976bd |
| Rocky Linux:8 | nodejs | before 1:20.19.2-1.module+el8.10.0+1988+437f3d23 | 1:20.19.2-1.module+el8.10.0+1988+437f3d23 |
+35
Same product
nodejs: all recordsOther 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 f58Plan
- 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.34Monitor
- CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-23165May 18, 2025 · In Node.js, the `ReadFileUtf8` internal binding leaks memory due to a corrupted pointer in `uv_fs_s.file`: a UTF-16 path buffer is allocated14Monitor
- ← EarlierCVE-2025-23166May 18, 2025 · The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background t30Monitor
- Later →CVE-2025-27209Jul 18, 2025 · The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash.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 / package | Fixed version | Source |
|---|---|---|
| nodejs node | 10.* | Vendor (CNA) |
| nodejs node | 11.* | Vendor (CNA) |
| nodejs node | 12.* | Vendor (CNA) |
| nodejs node | 13.* | Vendor (CNA) |
| nodejs node | 14.* | Vendor (CNA) |
| nodejs node | 15.* | Vendor (CNA) |
| nodejs node | 16.* | Vendor (CNA) |
| nodejs node | 17.* | Vendor (CNA) |
| nodejs node | 18.* | Vendor (CNA) |
| nodejs node | 19.* | Vendor (CNA) |
| nodejs node | 4.* | Vendor (CNA) |
| nodejs node | 5.* | Vendor (CNA) |
| nodejs node | 6.* | Vendor (CNA) |
| nodejs node | 7.* | Vendor (CNA) |
| nodejs node | 8.* | Vendor (CNA) |
| nodejs node | 9.* | Vendor (CNA) |
| azl3 fluent-bit 3.1.9-4 on Azure Linux 3.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 fluent-bit 3.0.6-2 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 nodejs18 18.20.3-12 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:node-undici | 7.15.0+dfsg+~cs3.2.0-1 · Debian:14 | Package registry (OSV) |
| opensuse:nodejs20 | 20.19.2-150600.3.12.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:nodejs | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-full-i18n | 1:20.19.2-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:3.0.1-1.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-packaging | 0:2021.06-4.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-packaging-bundler | 0:2021.06-4.module+el9.6.0+23146+be9976bd · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+8
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2025-07-15 |
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.
- Published
- First PoC+57 d
- TodayNov 7, 2026+537 d
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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-2024-27982376 days apartThe team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to 26Monitor
- CVE-2026-58044443 days apartA flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from 14Monitor
- CVE-2026-48932470 days apartA flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from 14Monitor
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
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
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:L/I:L/A:N
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.