undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explicit Cache-Control directive is stored and later replayed from cache. Because response headers from a remote origin are untrusted, an origin can answer once with a cacheable status and then have the client's own subsequent state-changing requests to that path served from the stale cache entry without ever reaching the origin, an integrity failure that occurs under the interceptor's default configuration. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
References
| Link | Resource |
|---|---|
| https://cna.openjsf.org/security-advisories.html | Third Party Advisory |
| https://github.com/nodejs/undici/security/advisories/GHSA-8436-99hf-9mmv | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-09-04 17:17
Updated : 2026-09-15 14:20
NVD link : CVE-2026-85008
Mitre link : CVE-2026-85008
CVE.ORG link : CVE-2026-85008
JSON object : View
Products Affected
nodejs
- undici
CWE
CWE-345
Insufficient Verification of Data Authenticity