BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-23167High confidence

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`

nodejs · node

6.5MediumCVSS 3.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.51% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs nodejs node and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-undiciAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenode-undiciAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcellhttpNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenode-undiciVendor fix publishedDebian records a fixed source-package version for this release.7.15.0+dfsg+~cs3.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcellhttpNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenode-undiciVendor fix publishedDebian records a fixed source-package version for this release.7.15.0+dfsg+~cs3.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-23167 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2025-23167
49 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • nodejs8 as component of SLES-LTSS-TERADATA 15 SP2
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-27706

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-444 ↗

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'). 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-444
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1055Node.js: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen oder Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1089Multiples vulnérabilités dans Tenable Enclave Security

d?id=CVE-2023-39332 Référence CVE CVE-2024-21892 https://www.cve.org/CVERecord?id=CVE-2024-21892 Référence CVE CVE-2024-21896 https://www.cve.org/CVERecord?id=CVE-2024-21896 Référence CVE CVE-2024-22017 https://www.cve.org/CVERecord?id=CVE-2024-22017 Référence CVE CVE-2024-22019 https://www.cve.org/CVERecord?id=CVE-2024-22019 Référence CVE CVE-2024-27980 https://www.cve.org/CVERecord?id=CVE-2024-27980 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-36138 https://www.cve.org/CVERecord?id=CVE-2024-36138 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-55130 https://www.cve.org/CVERecord?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-27140 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-24014 https://www.cve.org/CVERecord?id=CVE-2025-24014 Référence CVE CVE-2025-24293 https://www.cve.org/CVERecord?id=CVE-2025-24293 Référence CVE CVE-2025-24294 https://www.cve.org/CVERecord?id=CVE-2025-24294 Référence CVE CVE-2025-24813 https://www.cve.org/CVERecord?id=CVE-2025-24813 Référence CVE CVE-2025-24855 https://www.cve.org/CVERecord?id=CVE-2025-24855 Référence CVE CVE-2025-24928 https://www.cve.org/CVERecord?id=CVE-2025-24928 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-25186 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-24293 https://www.cve.org/CVERecord?id=CVE-2025-24293 Référence CVE CVE-2025-25186 https://www.cve.org/CVERecord?id=CVE-2025-25186 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-30681 https://www.cve.org/CVERecord?id=CVE-2025-30681 Référence CVE CVE-2025-30682 https://www.cve.org/CVERecord?id=CVE-2025-30682 Référence CVE CVE-2025-30683 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0751Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-21581 Référence CVE CVE-2025-21584 https://www.cve.org/CVERecord?id=CVE-2025-21584 Référence CVE CVE-2025-21585 https://www.cve.org/CVERecord?id=CVE-2025-21585 Référence CVE CVE-2025-21588 https://www.cve.org/CVERecord?id=CVE-2025-21588 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23048 https://www.cve.org/CVERecord?id=CVE-2025-23048 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-27209 https://www.cve.org/CVERecord?id=CVE-2025-27209 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-30399 https://www.cve.org/CVERecord?id=CVE-2025-30399 Référence CVE CVE-2025-30681 https://www.cve.org/CVERecord?id=CVE-2025-30681 Référence CVE CVE-2025-30682 https://www.cve.org/CVERecord?id=CVE-2025-30682 Référence CVE CVE-2025-30683 https://www.cve.org/CVERecord?id=CVE-2025-30683 Référence CVE CVE-2025-30684 https://www.cve.org/CVERecord?id=CVE-2025-30684 Référence CVE CVE-2025-30685 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0621Multiples vulnérabilités dans les produits Tenable

De multiples vulnérabilités ont été découvertes dans Tenable Identity Exposure. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0434Multiples vulnérabilités dans Node.js

De multiples vulnérabilités ont été découvertes dans Node.js. Elles permettent à un attaquant de provoquer un déni de service à distance et un contournement de la politique de sécurité.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 May 2025 · Last source change 27 May 2025, 18:31 UTC · CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-27706
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2025-27706↗SUSE Product Security Team security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-23167 · cve.blacktree.nl