Advisory

GHSA-pr7r-676h-xcf6

Also known as: CVE-2026-9678

Summary

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

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-18 14:28 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

undici

npm · All systems

Affected

  • introduced 7.0.0, fixed 7.28.0 (semver)

Fixed versions

7.28.0

Fix

undici

npm · All systems

Affected

  • introduced 8.0.0, fixed 8.5.0 (semver)

Fixed versions

8.5.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences