CVE-2026-117518
@fastify/reply-from vulnerable to path traversal via backslash dot-segment prefix escape
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-117518 divulgada · CVSS 8.2 (CNA) | |
| Remediación | Parche 12.8.1 | @fastify/reply-from · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The @fastify/reply-from plugin, which forwards requests from Fastify applications to upstream HTTP servers, is affected. A crafted request using backslash path segments can bypass the plugin's path checks and reach upstream endpoints outside the intended prefix, potentially exposing unauthorized data with limited risk to data integrity.
Affects @fastify/reply-from 12.8.0 and earlier when proxying to an upstream prefix or relying on route guards in front of reply.from(). Fixed in 12.8.1.
Descripción original del registro (openjs)
@fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions up to and including 12.8.0, the plugin validated proxy paths against forward-slash dot-segments only and then built the target with the WHATWG URL parser, which normalizes a backslash and its percent-encoded form to a forward slash on the http, https, ws, and wss schemes. A path that uses backslash dot-segments therefore bypasses the traversal check and resolves to a different upstream path, so an application that scopes proxying to an upstream prefix, or relies on route guards in front of the forwarding call, can have an unauthenticated request escape the intended prefix and reach other upstream endpoints. The resulting access to unintended upstream resources is primarily a confidentiality impact with limited integrity impact. The issue is fixed in @fastify/reply-from 12.8.1, where the path is normalized and any segment resolving to a single or double dot, along with control characters and ambiguous whitespace, is rejected before the URL is constructed, and users should upgrade to 12.8.1 or later. There is no workaround other than upgrading.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@fastify/reply-from |
Corregida | 12.8.1 | 0 d | 12.8.2 no afectada |
12.8.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-vp2r-3vgv-32g9https://cna.openjsf.org/security-advisories.htmlLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
