CVE-2026-16158 @fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collision
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
Description
Impact: @fastify/reply-from versions from 8.3.1 up to but not including 12.6.4 build the internal URL cache key by concatenating the destination and source path without a delimiter. Different destination and source pairs can therefore produce the same key while resolving to different upstream URLs. When getUpstream selects an upstream from request data, a URL cached for one upstream can be reused for a request intended for another upstream, causing cross-upstream data access and modification. The default configuration is affected. Setting disableCache to true prevents the behavior. Patches: upgrade to @fastify/reply-from 12.6.4. Workarounds: pass disableCache: true when registering the plugin.
Upgrade path
2 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| @fastify/reply-from | >= 8.3.1, < 12.6.4 | 12.6.4 | Fixed |
| fastifyreply-from | >= 8.3.1, < 12.6.4 | 12.6.4 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| @fastify/reply-from | >= 8.3.1, < 12.6.4 | 12.6.4 |
| fastifyreply-from | >= 8.3.1, < 12.6.4 | 12.6.4 |
References
- github.com vendor-advisory
- cna.openjsf.org vendor-advisory
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2502033 issue-tracking
- www.cve.org
- nvd.nist.gov