CVE-2026-117549
@fastify/secure-session vulnerable to signature verification bypass via cookie signature removal
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-117549 divulgada · CVSS 4.2 (CNA) | |
| Remediación | Parche 8.4.2 | @fastify/secure-session · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The @fastify/secure-session plugin for Fastify, used to store encrypted sessions in cookies when signed cookies are enabled, is affected. An attacker who already holds an old, unexpired session cookie can strip its invalidated signature and keep using that session after the signing secret has been rotated, though they cannot forge data or survive rotation of the encryption key.
Only affects @fastify/secure-session 7.5.0 through 8.4.2 when the plugin is configured with cookie.signed: true. Fixed in 8.4.2.
Descripción original del registro (openjs)
@fastify/secure-session is a session plugin for Fastify that stores an encrypted session in a cookie. In versions 7.5.0 through 8.4.1, when the plugin is configured with the signed cookie option, it calls the cookie unsign routine but, when the signature check reports the value as invalid, still passes the original cookie value to the session decoder, so a session whose signature did not validate is decrypted anyway. The practical effect appears when an application supplies the cookie signing secret independently of the session encryption key and rotates only the signing secret to retire existing sessions while keeping the encryption key active, because a holder of an old session cookie can strip the now obsolete signature and keep using the session. The attacker must already possess an unexpired encrypted session cookie and needs neither secret, and cannot forge session data, extend expiry, or survive rotation of the encryption key. The issue is fixed in @fastify/secure-session 8.4.2, which no longer decodes the session when the signed cookie option is set and the signature check fails, and users should upgrade to 8.4.2 or later. As a workaround, rotate the session encryption key rather than relying on rotation of the cookie signing secret alone.
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/secure-session |
Corregida | 8.4.2 | 0 d | 8.4.2 no afectada |
8.4.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/fastify/fastify-secure-session/security/advisories/GHSA-4cgq-x5f7-r8jvhttps://cna.openjsf.org/security-advisories.htmlLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
