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`. 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: 2025-05-19 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-23167 is rated Low Risk (35.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.10%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-23167

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-15 0.01% 0.10% +0.09%
2 2025-11-21 0.06% 0.01% -0.05%
3 2025-11-18 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23167

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2025-23167

OS Trackers for CVE-2025-23167

vendor priority summary link
debian unimportant CVE-2025-23167 unimportant priority: Debian including 2 source packages (llhttp, node-undici), 6 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 4, open 2. https://security-tracker.debian.org/tracker/CVE-2025-23167
redhat medium — https://access.redhat.com/security/cve/CVE-2025-23167
suse medium CVE-2025-23167 severity moderate: SUSE including 43 source package names (0.6.9-10.19:nodejs20-20.19.2-150600.3.12.1, corepack20-20.19.2-150600.3.12.1, …), 161 product×package rows across 23 product lines (Container containers/open-webui, SLES-LTSS-TERADATA 15 SP2, … (23 product lines)): Known Not Affected 127, Fixed 34. https://www.suse.com/security/cve/CVE-2025-23167/
ubuntu medium CVE-2025-23167 medium priority: Ubuntu has no source package entries, 0 status rows across 0 suites (none): no status rows. https://ubuntu.com/security/CVE-2025-23167

Affected software / configurations for CVE-2025-23167

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-23167

cvelogic Threat Intelligence