@Fastify/Reply From
Approved changes feed: RSS · Atom
cpe:2.3:a:@fastify/reply-from:@fastify/reply-from:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | @Fastify/Reply From (ee3361be-d0df-57ae-ac51-a21fcec721ab) |
|---|---|
| Product | @Fastify/Reply From (91b36e98-1aff-54b8-91b1-3e46e90d6bfe) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-16158 |
vulnerable | 2026-07-29 00:26:18.562492 |
@fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collision
HIGH (8.7)
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.
Published: 2026-07-18T12:28:17.262Z
Updated: 2026-07-20T15:15:50.016Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33805 |
vulnerable | 2026-06-08 07:59:11.243117 |
@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers
@fastify/reply-from v12.6.1 and earlier and @fastify/http-proxy v11.4.3 and earlier process the client's Connection header after the proxy has added its own headers via rewriteRequestHeaders. This allows attackers to retroactively strip proxy-added headers from upstream requests by listing them in the Connection header value. Any header added by the proxy for routing, access control, or security purposes can be selectively removed by a client. @fastify/http-proxy is also affected as it delegates to @fastify/reply-from.
Upgrade to @fastify/reply-from v12.6.2 or @fastify/http-proxy v11.4.4 or later.
Published: 2026-04-15T10:13:25.147Z
Updated: 2026-07-15T01:06:04.635Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.