Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

@fastify/secure-session: Reuse of destroyed secure session cookie

CVE-2024-31999GHSA-9wwp-q7wq-jx35

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@fastify/secure-session 7.3.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
  • CVE-2024-31999: 0.62% estimated exploitation activity in the next 30 days; percentile 49.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact At the end of the request handling, it will encrypt all data in the session with a secret key and attach the ciphertext as a cookie value with the defined cookie name. After that, the session on the server side is destroyed. When an encrypted cookie with matching session name is provided with subsequent requests, it will decrypt the ciphertext to get the data. The plugin then creates a new session with the data in the ciphertext. Thus theoretically the web instance is still accessing the data from a server-side session, but technically that session is generated solely from a user provided cookie (which is assumed to be non-craftable because it is encrypted with a secret key not known to the user). The issue exists in the session removal process. In the delete function of the code, when the session is deleted, it is marked for deletion. However, if an attacker could gain access to the cookie, they could keep using it forever. Patches Fixed in…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-9wwp-q7wq-jx35

  2. Revision 1 · created ·

    Published from osv record GHSA-9wwp-q7wq-jx35

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-31999

Advisory: @fastify/secure-session: Reuse of destroyed secure session cookie
IDs: CVE-2024-31999, GHSA-9wwp-q7wq-jx35
Record: https://patchnext.com/advisories/cve-2024-31999 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @fastify/secure-session 7.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @fastify/secure-session: affected < 7.3.0; fixed in 7.3.0

## Suggested inspection (read-only)
- `npm ls @fastify/secure-session --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @fastify/secure-session.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9wwp-q7wq-jx35 (OSV record GHSA-9wwp-q7wq-jx35 lists affected ranges: npm @fastify/secure-session >=0 <7.3.0 (fixed))
- Verified: https://github.com/advisories/GHSA-9wwp-q7wq-jx35 (GitHub-reviewed advisory GHSA-9wwp-q7wq-jx35 lists affected ranges: npm @fastify/secure-session >=0 <7.3.0)

Commands are suggestions: review each one before running it.

Loading voting…