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

undici vulnerable to cross-user information disclosure via shared cache whitespace bypass

CVSS 3.1 5.9 MEDIUMEUVD CVSS 3.1 5.9 CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary 5.9 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by undici 7.28.0Fixed by undici 8.5.0KEV status unknown
Original advisory

cve-program · CVE-2026-9678

Published

Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives. Patches: Upgrade to undici v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.

Read the publisher's advisory

euvd · EUVD-2026-37766

Published

Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives. Patches: Upgrade to undici v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.

Read the publisher's advisory

nvd · CVE-2026-9678

Published

Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives. Patches: Upgrade to undici v7.28.0 or v8.5.0. Workarounds: If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.

Read the publisher's advisory

osv · GHSA-pr7r-676h-xcf6

Published

## Impact Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream `Cache-Control` header uses whitespace-padded qualified `private` or `no-cache` field names such as `private=" authorization"` or `no-cache="\tauthorization"`. The parser preserves the surrounding whitespace, so later comparisons against the literal `authorization` field name fail and the response is stored. In shared-cache mode, this allows a response containing one user's authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key. Affected applications are those that explicitly enable the cache interceptor (`interceptors.cache()`) in shared mode, forward `Authorization` headers upstream, and receive cacheable responses with non-canonical qualified `private` or `no-cache` directives. ## Patches Upgrade to undici v7.28.0 or v8.5.0. ## Workarounds If upgrade is not immediately possible, disable shared-cache mode for traffic that includes `Authorization` headers, avoid caching responses to authenticated requests, or add `Vary: Authorization` upstream.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-9678

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": "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-37766

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:04:09 PM

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

15 related source bulletins · separate from aliases

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

CVE-2026-6734 · CVE-2026-9675 · CVE-2026-9678 · CVE-2026-9697 · CVE-2026-45149

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

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

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

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

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

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

CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59464 · CVE-2026-2950 · CVE-2026-6734 · CVE-2026-9675 · CVE-2026-9678 · CVE-2026-9697 · CVE-2026-45149 · CVE-2026-48615 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48936 · CVE-2026-59868 · CVE-2026-59870

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

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

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

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

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

Original publisher date fields

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

lastModified: 2026-06-25T17:44:16.007

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-pr7r-676h-xcf6

Published

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 11:08 UTC · 256 of 275 readable · 252 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.