Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

CVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 9.8 CRITICALCVSS_V3 Publisher rating MODERATEFixed by undici 6.24.0Fixed by undici 7.24.0KEV status unknown

cve-program · CVE-2026-1525

Published

Undici allows duplicate HTTP Content-Length headers when they are provided in an array with case-variant names (e.g., Content-Length and content-length). This produces malformed HTTP/1.1 requests with multiple conflicting Content-Length values on the wire. Who is impacted: * Applications using undici.request(), undici.Client, or similar low-level APIs with headers passed as flat arrays * Applications that accept user-controlled header names without case-normalization Potential consequences: * Denial of Service: Strict HTTP parsers (proxies, servers) will reject requests with duplicate Content-Length headers (400 Bad Request) * HTTP Request Smuggling: In deployments where an intermediary and backend interpret duplicate headers inconsistently (e.g., one uses the first value, the other uses the last), this can enable request smuggling attacks leading to ACL bypass, cache poisoning, or credential hijacking

Read the publisher's advisory

euvd · EUVD-2026-11685

Published

Undici allows duplicate HTTP Content-Length headers when they are provided in an array with case-variant names (e.g., Content-Length and content-length). This produces malformed HTTP/1.1 requests with multiple conflicting Content-Length values on the wire. Who is impacted: * Applications using undici.request(), undici.Client, or similar low-level APIs with headers passed as flat arrays * Applications that accept user-controlled header names without case-normalization Potential consequences: * Denial of Service: Strict HTTP parsers (proxies, servers) will reject requests with duplicate Content-Length headers (400 Bad Request) * HTTP Request Smuggling: In deployments where an intermediary and backend interpret duplicate headers inconsistently (e.g., one uses the first value, the other uses the last), this can enable request smuggling attacks leading to ACL bypass, cache poisoning, or credential hijacking

Read the publisher's advisory

nvd · CVE-2026-1525

Published

Undici allows duplicate HTTP Content-Length headers when they are provided in an array with case-variant names (e.g., Content-Length and content-length). This produces malformed HTTP/1.1 requests with multiple conflicting Content-Length values on the wire. Who is impacted: * Applications using undici.request(), undici.Client, or similar low-level APIs with headers passed as flat arrays * Applications that accept user-controlled header names without case-normalization Potential consequences: * Denial of Service: Strict HTTP parsers (proxies, servers) will reject requests with duplicate Content-Length headers (400 Bad Request) * HTTP Request Smuggling: In deployments where an intermediary and backend interpret duplicate headers inconsistently (e.g., one uses the first value, the other uses the last), this can enable request smuggling attacks leading to ACL bypass, cache poisoning, or credential hijacking

Read the publisher's advisory

osv · GHSA-2mjp-6q6p-2qxm

Published

### Impact Undici allows duplicate HTTP `Content-Length` headers when they are provided in an array with case-variant names (e.g., `Content-Length` and `content-length`). This produces malformed HTTP/1.1 requests with multiple conflicting `Content-Length` values on the wire. **Who is impacted:** - Applications using `undici.request()`, `undici.Client`, or similar low-level APIs with headers passed as flat arrays - Applications that accept user-controlled header names without case-normalization **Potential consequences:** - **Denial of Service**: Strict HTTP parsers (proxies, servers) will reject requests with duplicate `Content-Length` headers (400 Bad Request) - **HTTP Request Smuggling**: In deployments where an intermediary and backend interpret duplicate headers inconsistently (e.g., one uses the first value, the other uses the last), this can enable request smuggling attacks leading to ACL bypass, cache poisoning, or credential hijacking ### Patches Patched in the undici version v7.24.0 and v6.24.0. Users should upgrade to this version or later. ### Workarounds If upgrading is not immediately possible: 1. **Validate header names**: Ensure no duplicate `Content-Length` headers (case-insensitive) are present before passing headers to undici 2. **Use object format**: Pass headers as a plain object (`{ 'content-length': '123' }`) rather than an array, which naturally deduplicates by key 3. **Sanitize user input**: If headers originate from user input, normalize header names to lowercase and reject duplicates

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-1525

Published

undici

https://github.com/nodejs/undici/

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "undici",
                    "product": "undici",
                    "collectionURL": "https://github.com/nodejs/undici/",
                    "packageName": "undici",
                    "repo": "https://github.com/nodejs/undici/",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "< 6.24.0; 7.0.0 < 7.24.0"
                        },
                        {
                            "status": "unaffected",
                            "version": "6.24.0: 7.24.0"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-11685

Published

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, 7:56:55 PM

dateUpdated: Mar 12, 2026, 8:46:13 PM

15 related source bulletins · separate from aliases

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

RHSA-2026:7983: Red Hat Security Advisory: nodejs:22 security update

CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-21710 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135 · CVE-2026-27904

RHSA-2026:17789: Red Hat Security Advisory: Red Hat build of Cryostat 4.2.0: new RHEL 9 container image security update

CVE-2026-1002 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-33186 · CVE-2026-33813 · CVE-2026-33815 · CVE-2026-33816 · CVE-2026-33870 · CVE-2026-33871 · CVE-2026-34986 · CVE-2026-39852 · CVE-2026-40895

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:21772: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.28.0 Release.

CVE-2025-14813 · CVE-2025-68121 · CVE-2026-0636 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-1605 · CVE-2026-2229 · CVE-2026-2327 · CVE-2026-5588 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-29074 · CVE-2026-30827 · CVE-2026-31802 · CVE-2026-32141 · CVE-2026-32280 · CVE-2026-32282 · CVE-2026-32305 · CVE-2026-33252 · CVE-2026-33810 · CVE-2026-34742 · CVE-2026-35051 · CVE-2026-39858 · CVE-2026-40477 · CVE-2026-40478 · CVE-2026-40611 · CVE-2026-40895 · CVE-2026-40912 · CVE-2026-40972 · CVE-2026-40973 · CVE-2026-40975 · CVE-2026-41240 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42039 · CVE-2026-42041 · CVE-2026-42043 · CVE-2026-42044

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

RHSA-2026:7080: Red Hat Security Advisory: nodejs22 security update

CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-21710 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135 · CVE-2026-27904

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

RHSA-2026:9742: Red Hat Security Advisory: Red Hat Developer Hub 1.8.6 release.

CVE-2025-62718 · CVE-2025-69534 · CVE-2025-69873 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-3118 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-25679 · CVE-2026-26996 · CVE-2026-27601 · CVE-2026-27904 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-29186 · CVE-2026-32141 · CVE-2026-33036 · CVE-2026-33228 · CVE-2026-33891 · CVE-2026-33894 · CVE-2026-33895 · CVE-2026-33896 · CVE-2026-39983 · CVE-2026-40175

RHSA-2026:7123: Red Hat Security Advisory: nodejs:22 security update

CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-21710 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135 · CVE-2026-27904

RHSA-2026:13826: Red Hat Security Advisory: Red Hat Developer Hub 1.9.4 release.

CVE-2025-62718 · CVE-2025-69534 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-3118 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-27601 · CVE-2026-27904 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-29186 · CVE-2026-32141 · CVE-2026-32280 · CVE-2026-32282 · CVE-2026-33228 · CVE-2026-33891 · CVE-2026-33894 · CVE-2026-33895 · CVE-2026-33896 · CVE-2026-39983 · CVE-2026-40175 · CVE-2026-40895

RHSA-2026:7310: Red Hat Security Advisory: nodejs22 security update

CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-21710 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135 · CVE-2026-27904

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:7302: Red Hat Security Advisory: nodejs:22 security update

CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-21710 · CVE-2026-25547 · CVE-2026-26996 · CVE-2026-27135 · CVE-2026-27904

RHSA-2026:73987: Red Hat Security Advisory: RHOAI 3.3.7 - Red Hat OpenShift AI

CVE-2025-61726 · CVE-2025-66471 · CVE-2025-71408 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-5422 · CVE-2026-6321 · CVE-2026-6734 · CVE-2026-9697 · CVE-2026-11816 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-15154 · CVE-2026-15378 · CVE-2026-16221 · CVE-2026-16745 · CVE-2026-18951 · CVE-2026-23490 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27489 · CVE-2026-27893 · CVE-2026-28356 · CVE-2026-28500 · CVE-2026-28684 · CVE-2026-31230 · CVE-2026-31958 · CVE-2026-32274 · CVE-2026-32286 · CVE-2026-32597 · CVE-2026-33186 · CVE-2026-33231 · CVE-2026-33245 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-33815 · CVE-2026-33816 · CVE-2026-34445 · CVE-2026-34986 · CVE-2026-34993 · CVE-2026-35397 · CVE-2026-35536 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-40110 · CVE-2026-41242 · CVE-2026-42215 · CVE-2026-42294 · CVE-2026-42296 · CVE-2026-42297 · CVE-2026-42338 · CVE-2026-42502 · CVE-2026-42508 · CVE-2026-44240 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44727 · CVE-2026-44843 · CVE-2026-45736 · CVE-2026-46595 · CVE-2026-48526 · CVE-2026-48586 · CVE-2026-48710 · CVE-2026-48746 · CVE-2026-48779 · CVE-2026-49855 · CVE-2026-53550 · CVE-2026-54058 · CVE-2026-54283 · CVE-2026-55969 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59884 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-62384 · CVE-2026-63310 · CVE-2026-64834 · CVE-2026-64835 · CVE-2026-66036 · CVE-2026-66037 · CVE-2026-66038 · CVE-2026-66040 · CVE-2026-67322 · CVE-2026-67323 · CVE-2026-67325 · CVE-2026-68770 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-69243 · CVE-2026-69244 · CVE-2026-71281 · CVE-2026-73089 · CVE-2026-73415 · CVE-2026-73417 · CVE-2026-73627 · CVE-2026-78682 · CVE-2026-79674 · CVE-2026-79675 · CVE-2026-80205 · CVE-2026-81722 · CVE-2026-81724 · CVE-2026-81727 · CVE-2026-84375 · CVE-2026-84445

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-1525

Published

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-444

Original publisher date fields

published: 2026-03-12T20:16:02.670

lastModified: 2026-06-17T10:15:59.927

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.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-2mjp-6q6p-2qxm

Published

undici

npm

SEMVER · introduced 0 → fixed 6.24.0

undici

npm

SEMVER · introduced 7.0.0 → fixed 7.24.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 03:41 UTC · 274 of 275 readable · 259 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current