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 · Vulnerability

CVSS 3.1 5.9 MEDIUMEUVD CVSS 3.1 5.9 CVSS 3.1 · [email protected] · Secondary 5.9 MEDIUMCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating MODERATEFixed by undici 7.18.2Fixed by undici 6.23.0KEV status unknown

cve-program · CVE-2026-22036

Published

Undici is an HTTP/1.1 client for Node.js. Prior to 7.18.0 and 6.23.0, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. This vulnerability is fixed in 7.18.0 and 6.23.0.

Read the publisher's advisory

euvd · EUVD-2026-2422

Published

Undici is an HTTP/1.1 client for Node.js. Prior to 7.18.0 and 6.23.0, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. This vulnerability is fixed in 7.18.0 and 6.23.0.

Read the publisher's advisory

nvd · CVE-2026-22036

Published

Undici is an HTTP/1.1 client for Node.js. Prior to 7.18.0 and 6.23.0, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. This vulnerability is fixed in 7.18.0 and 6.23.0.

Read the publisher's advisory

osv · GHSA-g9mf-h72j-4rw9

Published

### Impact The `fetch()` API supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, br). This is also supported by the undici decompress interceptor. However, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation. ### Patches Upgrade to 7.18.2 or 6.23.0. ### Workarounds It is possible to apply an undici interceptor and filter long `Content-Encoding` sequences manually. ### References * https://hackerone.com/reports/3456148 * https://github.com/advisories/GHSA-gm62-xv2j-4w53 * https://curl.se/docs/CVE-2022-32206.html

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-22036

Published

undici

Vendor product

Publisher's version information

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

{
                    "vendor": "nodejs",
                    "product": "undici",
                    "versions": [
                        {
                            "version": "< 6.23.0",
                            "status": "affected"
                        },
                        {
                            "version": ">= 7.0.0, < 7.18.2",
                            "status": "affected"
                        }
                    ]
                }

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

euvd · EUVD-2026-2422

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: Jan 14, 2026, 7:07:13 PM

dateUpdated: Jan 22, 2026, 8:17:20 PM

14 related source bulletins · separate from aliases

openSUSE-SU-2026:10074-1: corepack22-22.22.0-1.1 on GA media

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

SUSE-SU-2026:0457-1: Security update for nodejs20

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

SUSE-SU-2026:4248-1: Security update for nodejs18

CVE-2025-22150 · CVE-2025-23166 · CVE-2025-23167 · CVE-2025-55131 · CVE-2025-59465 · CVE-2025-59466 · CVE-2025-62408 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-15157 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21717 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-56846 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-9679

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

openSUSE-SU-2026:20236-1: Security update for nodejs22

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

SUSE-SU-2026:0435-1: Security update for nodejs20

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

SUSE-SU-2026:3929-1: Security update for nodejs20

CVE-2025-22150 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-40170 · CVE-2026-42338 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-54272 · CVE-2026-56846 · CVE-2026-56847 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58039 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-69192 · CVE-2026-9496 · CVE-2026-9679

openSUSE-SU-2026:10075-1: corepack24-24.13.0-2.1 on GA media

CVE-2026-22036

SUSE-SU-2026:0295-1: Security update for nodejs22

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

SUSE-SU-2026:20436-1: Security update for nodejs22

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

RHSA-2026:24841: Red Hat Security Advisory: Red Hat Developer Hub 1.10.0 release.

CVE-2026-2950 · CVE-2026-4923 · CVE-2026-22036 · CVE-2026-27601 · CVE-2026-31988 · CVE-2026-32235 · CVE-2026-33349

SUSE-SU-2026:3930-1: Security update for nodejs20

CVE-2025-22150 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-40170 · CVE-2026-42338 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-54272 · CVE-2026-56846 · CVE-2026-56847 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58039 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-69192 · CVE-2026-9496 · CVE-2026-9679

SUSE-SU-2026:0301-1: Security update for nodejs22

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-22036

openSUSE-SU-2026:11110-1: nodejs26-26.3.1-1.1 on GA media

CVE-2024-21538 · CVE-2024-22018 · CVE-2024-22020 · CVE-2024-36137 · CVE-2024-36138 · CVE-2024-37372 · CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085 · CVE-2025-23165 · CVE-2025-23166 · CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59464 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21712 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · CVE-2026-22036 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48936

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

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: Modified

Weakness classifications: CWE-770

Original publisher date fields

published: 2026-01-14T19:16:47.833

lastModified: 2026-06-17T10:19:24.020

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-g9mf-h72j-4rw9

Published

undici

npm

SEMVER · introduced 7.0.0 → fixed 7.18.2

undici

npm

SEMVER · introduced 0 → fixed 6.23.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 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current