@fastify/session is a session plugin for Fastify. In all releases before 11.1.6, with the default rolling session behavior, a request that restored a session before a logout could save its own copy after another request had completed the session destroy call, recreating the destroyed session identifier with its authenticated data. An attacker who already holds a victim's valid signed session cookie and keeps a request in flight across the logout can replay that cookie to restore the session after it was meant to be revoked, without any cookie theft or signature forgery. The issue is fixed in @fastify/session 11.1.6, which adds a per session generation marker and a conditional store write so a session restored before a logout or regeneration cannot recreate or overwrite the current entry, and users should upgrade to 11.1.6 or later. There is no workaround, and custom session stores must implement the new conditional write.
Severity
CVSS 3.1
3.7 low
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
EPSS
0.09%(unchanged from 0.09% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition) CWE-613Insufficient Session Expirationdeprecated by MITREsee CWE-1463, CWE-1464
Show the promptExplain CVE-2026-117499 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-117499?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-117499?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-117499 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
@fastify/session:@fastify/session
Versions
From the CNA's record in the CVE List.
Product
Affected
@fastify/session
before 11.1.6
Red Hat
Red Hat rates this Low.
Red Hat's statement
Red Hat has evaluated this issue as having a Low impact because successful exploitation relies on high attack complexity and strict prerequisites, requiring an adversary to already possess an active user cookie and synchronize concurrent requests during session termination. The vulnerability cannot be used to forge session signatures or exfiltrate tokens without prior access. Exposure is therefore restricted to specific race conditions when invalidating sessions in applications utilizing rolling session mechanisms.