undici is vulnerable to CRLF Injection via upgrade option
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-1527
PublishedImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }
- Source published
- 12 Mar 2026 20:17:18 UTC
- Source modified
- 13 Mar 2026 18:06:03 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
euvd · EUVD-2026-11701
PublishedImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 12, 2026, 8:17:18 PM
dateUpdated: Mar 13, 2026, 6:06:03 PM
7 related source bulletins · separate from aliases
RHSA-2026:7675: Red Hat Security Advisory: nodejs24 security update
CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1527 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-2581 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21711 · CVE-2026-21712 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135
RHSA-2026:7670: Red Hat Security Advisory: nodejs:24 security update
CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1527 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-2581 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21711 · CVE-2026-21712 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · CVE-2026-26996 · CVE-2026-27135
WID-SEC-W-2026-3621: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2022-35948 · CVE-2026-13697 · CVE-2026-14643 · CVE-2026-15157 · CVE-2026-1527 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-59871 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59875 · CVE-2026-92595 · CVE-2026-92596 · CVE-2026-92597 · CVE-2026-92598 · CVE-2026-9678
WID-SEC-W-2026-0933: IBM App Connect Enterprise (Hono und Undici): Mehrere Schwachstellen
CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-2581 · CVE-2026-29045 · CVE-2026-29085 · CVE-2026-29086 · CVE-2026-1527
RHSA-2026:7350: Red Hat Security Advisory: nodejs:24 security update
CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1527 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-2581 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21711 · CVE-2026-21712 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135
WID-SEC-W-2026-3596: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2022-35948 · CVE-2026-13149 · CVE-2026-14257 · CVE-2026-15157 · CVE-2026-1527 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-18149 · CVE-2026-18540 · CVE-2026-19534 · CVE-2026-2391 · CVE-2026-45820 · CVE-2026-54272 · CVE-2026-63670 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-69198 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-77037 · CVE-2026-77063 · CVE-2026-77078 · CVE-2026-82333 · CVE-2026-82417 · CVE-2026-82562 · CVE-2026-83605 · CVE-2026-83606 · CVE-2026-83607 · CVE-2026-83608 · CVE-2026-83609 · CVE-2026-83610 · CVE-2026-83611 · CVE-2026-83612 · CVE-2026-83613 · CVE-2026-83614 · CVE-2026-83615 · CVE-2026-83616 · CVE-2026-83618 · CVE-2026-83619 · CVE-2026-84292 · CVE-2026-84371 · CVE-2026-84375 · CVE-2026-84890 · CVE-2026-84933 · CVE-2026-84947 · CVE-2026-84961 · CVE-2026-85008 · CVE-2026-85014 · CVE-2026-85024 · CVE-2026-85152
RHSA-2026:56431: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18.27 security, enhancement & bug fix update
CVE-2025-61726 · CVE-2025-61729 · CVE-2025-64718 · CVE-2025-68470 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1527 · CVE-2026-2229 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9358 · CVE-2026-9679 · CVE-2026-9697 · CVE-2026-11525 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-22036 · CVE-2026-25645 · CVE-2026-33186 · CVE-2026-33349 · CVE-2026-33671 · CVE-2026-33672 · CVE-2026-33750 · CVE-2026-34043 · CVE-2026-34986 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-40181 · CVE-2026-41305 · CVE-2026-41650 · CVE-2026-41907 · CVE-2026-42342 · CVE-2026-45409 · CVE-2026-45736 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-53550 · CVE-2026-59869
- Source published
- Mar 12, 2026, 8:17:18 PM (timezone not stated)
- Source modified
- Mar 13, 2026, 6:06:03 PM (timezone not stated)
- Saved here
- 15 Nov 2026 07:32:50 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
nvd · CVE-2026-1527
PublishedImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-93
Original publisher date fields
published: 2026-03-12T21:16:25.137
lastModified: 2026-06-17T10:16:00.187
1 source CPE criteria · context only
- cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 12 Mar 2026 21:16:25 UTC
- Source modified
- 17 Jun 2026 10:16:00 UTC
- Saved here
- 25 Oct 2026 05:17:25 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary · 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
osv · GHSA-4992-7rv2-5pvq
Published### Impact When an application passes user-controlled input to the `upgrade` option of `client.request()`, an attacker can inject CRLF sequences (`\r\n`) to: 1. Inject arbitrary HTTP headers 2. Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the `upgrade` value directly to the socket without validating for invalid header characters: ```javascript // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` } ``` ### Patches Patched in the undici version v7.24.0 and v6.24.0. Users should upgrade to this version or later. ### Workarounds Sanitize the `upgrade` option string before passing to undici: ```javascript function sanitizeUpgrade(value) { if (/[\r\n]/.test(value)) { throw new Error('Invalid upgrade value') } return value } client.request({ upgrade: sanitizeUpgrade(userInput) }) ```
- Source published
- 13 Mar 2026 20:41:26 UTC
- Source modified
- 10 Sep 2026 03:50:37 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Publisher rating · MODERATE