Advisory

GHSA-8436-99hf-9mmv

Also known as: CVE-2026-85008

Summary

undici vulnerable to caching and replay of unsafe HTTP method responses

Details

Impact

undici's interceptors.cache() documents that it caches only safe HTTP methods. However, its internal skip-list is built by subtracting the configured methods from the safe-methods set, so an unsafe method (POST, PUT, PATCH, DELETE) never lands in the skip-list and is looked up against the cache store. Combined with the storage gate (canCacheResponse) having no method check, a heuristically-cacheable response (for example a 404) with an explicit Cache-Control: max-age=... to an unsafe method is stored and replayed on a subsequent identical request. The application's state-changing request never reaches the origin, and undici serves a fabricated response from the cache instead. This occurs with the default configuration (methods: ['GET']), which the public API does not allow widening to unsafe methods, so no application misuse is required; an untrusted origin can trigger it purely through its own response headers.

Patches

Upgrade to 7.29.1 or 8.10.2. The cache interceptor no longer reads from or writes to the cache for unsafe HTTP methods, while still invalidating existing cache entries on successful unsafe requests.

Workarounds

None.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-09-29 18:16 UTC
Modified
2026-09-29 18:28 UTC

Affected packages and fixes

undici

npm · All systems

Affected

  • introduced 7.0.0, fixed 7.29.1 (semver)

Fixed versions

7.29.1

Fix

undici

npm · All systems

Affected

  • introduced 8.0.0, fixed 8.10.2 (semver)

Fixed versions

8.10.2

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