CVE-2026-16158

published 18 Jul 2026 · updated 20 Jul 2026

@fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collision

8.7HighCVSS 8.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 12.6.4.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
@fastify/reply-from>=8.3.1 <12.6.412.6.4

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-16158 severity on Zeptric[![CVE-2026-16158](https://zeptric.io/badge/cve/CVE-2026-16158.svg)](https://zeptric.io/cve/CVE-2026-16158)