CVE-2026-117499: @fastify/session · Race Condition
Affects @fastify/sessionSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 11.1.6 when convenient.
Data as of 27 Oct 2026, 11:42 UTC
- Patch
- Available – fixed in 11.1.6
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade @fastify/session to 11.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/session@fastify/session | Affected
| Fixed in
|
npm@fastify/sessionpkg:npm/@fastify/sessionOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @fastify/session to version 11.1.6 or later, which includes the fix for this race condition. Custom session stores must implement the new conditional write logic introduced in 11.1.6 to prevent session restoration after logout. Users should ensure their session store is compatible with this fix.
Description
@fastify/session versions before 11.1.6 have a race condition vulnerability in the default rolling session behavior. This flaw allows an attacker who possesses a valid signed session cookie to replay that cookie across a logout event, restoring the session after it was intended to be destroyed. The issue arises because a request restoring a session before a logout can overwrite the destroyed session entry, effectively resurrecting the session without cookie theft or signature forgery. The vulnerability is fixed in version 11.1.6 by adding a per-session generation marker and conditional store writes to prevent session restoration or overwriting after logout.