Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.42% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-9678High confidence
undici vulnerable to cross-user information disclosure via shared cache whitespace bypass
undici · undici
Official source article: GitHub GHSA-PR7R-676H-XCF6 ↗. Check the applicable product and release in the original source.
5.9MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs undici undici and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | node-undici | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | node-undici | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | node-undici | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.5.0+dfsg+~cs3.2.0-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | node-undici | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.5.0+dfsg+~cs3.2.0-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | node-undici | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Open-source package ranges4 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmundici | >= 7.0.0, < 7.28.0 | 7.28.0 | GitHub advisory ↗upstream repository advisory · 24 Jun 2026 |
| npmundici | >= 8.0.0, < 8.5.0 | 8.5.0 | GitHub advisory ↗upstream repository advisory · 24 Jun 2026 |
| npmundici | SEMVER: introduced 7.0.0; fixed 7.28.0 | 7.28.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmundici | SEMVER: introduced 8.0.0; fixed 8.5.0 | 8.5.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-9678 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityundici: Undici: Information disclosure due to improper cache-control header parsing
The vendor explicitly identifies these products as affected by this CVE.
- cryostat-openshift-console-plugin-npm as a component of Cryostat 4
- grafana-infinity-datasource-npm as a component of Cryostat 4
- undici as a component of Cryostat 4
- openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines
- openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines
- openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines
- undici as a component of Red Hat AMQ Broker 7
- rh-podman-desktop.git as a component of Red Hat Build of Podman Desktop
- rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
- nodejs as a component of Red Hat Enterprise Linux 8
- nodejs-devel as a component of Red Hat Enterprise Linux 8
- nodejs-docs as a component of Red Hat Enterprise Linux 8
- Summary
- A flaw was found in Undici. The cache interceptor in shared-cache mode incorrectly classifies certain responses as cacheable due to improper handling of whitespace-padded Cache-Control header field names. This vulnerability allows an unauthenticated attacker to access authenticated user data from the cache, leading to information disclosure. This occurs when both authenticated and unauthenticated requests resolve to the same cache key.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Use of Cache Containing Sensitive Information → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-524 ↗
CWE-524: Use of Cache Containing Sensitive Information. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- cryostat-openshift-console-plugin-npm as a component of Cryostat 4
- grafana-infinity-datasource-npm as a component of Cryostat 4
- undici as a component of Cryostat 4
- openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines
- openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines
- openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines
- undici as a component of Red Hat AMQ Broker 7
- rh-podman-desktop.git as a component of Red Hat Build of Podman Desktop
- rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
- nodejs as a component of Red Hat Enterprise Linux 8
- nodejs-devel as a component of Red Hat Enterprise Linux 8
- nodejs-docs as a component of Red Hat Enterprise Linux 8
- nodejs-full-i18n as a component of Red Hat Enterprise Linux 8
- nodejs-libs as a component of Red Hat Enterprise Linux 8
- nodejs-nodemon as a component of Red Hat Enterprise Linux 8
- nodejs-nodemon.src as a component of Red Hat Enterprise Linux 8
- nodejs-packaging as a component of Red Hat Enterprise Linux 8
- nodejs-packaging-bundler as a component of Red Hat Enterprise Linux 8
- nodejs-packaging.src as a component of Red Hat Enterprise Linux 8
- nodejs.src as a component of Red Hat Enterprise Linux 8
- npm as a component of Red Hat Enterprise Linux 8
- v8-12.4-devel as a component of Red Hat Enterprise Linux 8
- v8-13.6-devel as a component of Red Hat Enterprise Linux 8
- rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- openshift4/ose-agent-installer-ui-rhel9 as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-monitoring-plugin-rhel9 as a component of Red Hat OpenShift Container Platform 4
- odf4/ocs-client-console-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/odf-console-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/odf-multicluster-console-rhel9 as a component of Red Hat Openshift Data Foundation 4
- and 6 more
- Fixed
- nodejs-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-debuginfo-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-debuginfo-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-debuginfo-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-debuginfo-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-devel-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-devel-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-devel-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-devel-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-docs-1:22.23.1-2.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-full-i18n-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-full-i18n-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-full-i18n-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-full-i18n-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-debuginfo-1:22.23.1-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-debuginfo-1:22.23.1-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-debuginfo-1:22.23.1-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-libs-debuginfo-1:22.23.1-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-npm-1:10.9.8-1.22.23.1.2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-npm-1:10.9.8-1.22.23.1.2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-npm-1:10.9.8-1.22.23.1.2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs-npm-1:10.9.8-1.22.23.1.2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- nodejs22-1:22.23.1-2.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
- and 217 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Jun 2026 · Last source change 17 Jun 2026, 18:05 UTC · CWE-524 · Use of Cache Containing Sensitive Information
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-37766
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.