AIKIDO-2026-868261
undici is vulnerable to Cache Poisoning
74
High Risk
This Affects:
undiciTL;DR
The cache and deduplicate interceptors omit the destination origin from their keys when composed onto a Client or Pool that does not carry a single authoritative origin. A cacheable or in-flight response from one upstream is then served for a matching request to a different, trusted origin. Shared interceptor state can therefore disclose another origin's response or persist a poisoned cache entry, including JWKS-style trust chains. The fix includes the destination origin in both interceptor keys.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you share interceptors.cache() or interceptors.deduplicate() state across more than one origin.
Background info
undici is vulnerable to Cache Poisoning in versions 8.10.0 - 8.10.1.
How to fix this
Upgrade the undici library to the patch version.
Links
GitHub Release
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.