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.
CVE-2026-16158
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EPSS
- 13.8%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026@fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collision · Advisory · fastify/fastify-reply-from · GitHub
https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-v574-6498-x57vSecurity Advisories | OpenJS Foundation CVE Numbering Authority
https://cna.openjsf.org/security-advisories.htmlWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:53 UTCEG score recompute
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 14:05 UTCEG score recompute
- 2026-07-18 12:40 UTCEG score recompute
- 2026-07-18 12:39 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-16158?
When was CVE-2026-16158 disclosed?
Is CVE-2026-16158 actively exploited?
What is the CVSS score of CVE-2026-16158?
How do I remediate CVE-2026-16158?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16158
Is Your Infrastructure Affected by CVE-2026-16158?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.