ChangeIntel IT change radar
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
CVE-2026-6733

undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse

CVSS 3.1 3.7 LOWEUVD CVSS 3.1 3.7 CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary 3.7 LOWCVSS_V3 Publisher rating LOWFixed by undici 6.27.0Fixed by undici 7.28.0Fixed by undici 8.5.0KEV status unknown
Original advisory

cve-program · CVE-2026-6733

Published

Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.

Read the publisher's advisory

euvd · EUVD-2026-37769

Published

Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.

Read the publisher's advisory

nvd · CVE-2026-6733

Published

Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.

Read the publisher's advisory

osv · GHSA-35p6-xmwp-9g52

Published

## Impact Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. ## Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. ## Workarounds Disable keep-alive connection reuse by setting `keepAliveTimeout: 0` on the Client or Pool.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-6733

Published

undici

Vendor product

Publisher's version information

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

{
                    "vendor": "undici",
                    "product": "undici",
                    "defaultStatus": "unaffected",
                    "versions": [
                        {
                            "versionType": "semver",
                            "status": "affected",
                            "version": "0",
                            "lessThan": "6.26.0"
                        },
                        {
                            "versionType": "semver",
                            "status": "unaffected",
                            "version": "6.26.0"
                        },
                        {
                            "versionType": "semver",
                            "status": "affected",
                            "version": "7.0.0",
                            "lessThan": "7.28.0"
                        },
                        {
                            "versionType": "semver",
                            "status": "unaffected",
                            "version": "7.28.0"
                        },
                        {
                            "versionType": "semver",
                            "status": "affected",
                            "version": "8.0.0",
                            "lessThan": "8.5.0"
                        },
                        {
                            "versionType": "semver",
                            "status": "unaffected",
                            "version": "8.5.0"
                        }
                    ],
                    "packageURL": "pkg:npm/undici"
                }

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

euvd · EUVD-2026-37769

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: Jun 17, 2026, 5:14:50 PM

dateUpdated: Jun 17, 2026, 6:30:26 PM

20 related source bulletins · separate from aliases

openSUSE-SU-2026:21236-1: Security update for nodejs24

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-2581 · 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-6733 · CVE-2026-9496 · CVE-2026-9678 · CVE-2026-9679

RHSA-2026:41947: Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-9678 · CVE-2026-11525 · CVE-2026-12151 · 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

RHSA-2026:38236: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-5078 · CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9678 · CVE-2026-9679 · CVE-2026-9697 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-53550 · CVE-2026-59869

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

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

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:11121-1: corepack24-24.17.0-1.1 on GA media

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-2581 · 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-6733 · CVE-2026-9496 · CVE-2026-9678 · CVE-2026-9679

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

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · 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-6733 · CVE-2026-9496 · CVE-2026-9679

SUSE-SU-2026:22565-1: Security update for nodejs24

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-2581 · 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-6733 · CVE-2026-9496 · CVE-2026-9678 · CVE-2026-9679

RHSA-2026:35842: Red Hat Security Advisory: nodejs22 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-9678 · CVE-2026-11525 · CVE-2026-12151 · 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

RHSA-2026:35841: Red Hat Security Advisory: nodejs24 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9678 · CVE-2026-9697 · CVE-2026-11525 · CVE-2026-12151 · 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

RHSA-2026:38009: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

CVE-2026-6733 · CVE-2026-9679 · CVE-2026-12151

WID-SEC-W-2026-2919: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2024-34459 · CVE-2025-10911 · CVE-2025-13151 · CVE-2025-5278 · CVE-2025-6170 · CVE-2025-66293 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-15308 · CVE-2026-15709 · CVE-2026-15711 · CVE-2026-15713 · CVE-2026-15714 · CVE-2026-31790 · CVE-2026-33416 · CVE-2026-33636 · CVE-2026-34180 · CVE-2026-34181 · CVE-2026-34182 · CVE-2026-34183 · CVE-2026-42338 · CVE-2026-42764 · CVE-2026-42766 · CVE-2026-42767 · CVE-2026-42768 · CVE-2026-42769 · CVE-2026-42770 · CVE-2026-42771 · CVE-2026-45445 · CVE-2026-45446 · CVE-2026-45447 · CVE-2026-47058 · CVE-2026-48615 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48864 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-5450 · CVE-2026-58016 · CVE-2026-65698 · CVE-2026-6733 · CVE-2026-6734 · CVE-2026-7383 · CVE-2026-8643 · CVE-2026-9076 · CVE-2026-9678 · CVE-2026-9697

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

CVE-2026-11525 · CVE-2026-12151 · 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-6733 · CVE-2026-9496 · CVE-2026-9679

WID-SEC-W-2026-2618: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-13676 · CVE-2026-53550 · CVE-2026-54285 · CVE-2026-59869 · CVE-2026-59877 · CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9675 · CVE-2026-9678 · CVE-2026-9679 · CVE-2026-9697

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

CVE-2026-11525 · CVE-2026-12151 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · 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-6733 · CVE-2026-9496 · CVE-2026-9679

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

RHSA-2026:39868: Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9678 · CVE-2026-9697 · CVE-2026-11525 · CVE-2026-12151 · 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

RHSA-2026:35892: Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-9678 · CVE-2026-11525 · CVE-2026-12151 · 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

RHSA-2026:35891: Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update

CVE-2026-6733 · CVE-2026-6734 · CVE-2026-9678 · CVE-2026-9697 · CVE-2026-11525 · CVE-2026-12151 · 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

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

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

Original publisher date fields

published: 2026-06-17T18:18:05.473

lastModified: 2026-06-27T23:46:06.553

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-35p6-xmwp-9g52

Published

undici

npm

SEMVER · introduced 0 → fixed 6.27.0

undici

npm

SEMVER · introduced 7.0.0 → fixed 7.28.0

undici

npm

SEMVER · introduced 8.0.0 → fixed 8.5.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 15 Nov 16:58 UTC · 254 of 275 readable · 250 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners.