Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 1.7amended

Turbo Frame responses can restore stale session cookies

CVE-2025-66803GHSA-qppm-g56g-fpvp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@hotwired/turbo 8.0.21), 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 4.0
1.7 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U · score source
EPSS
  • CVE-2025-66803: 0.28% estimated exploitation activity in the next 30 days; percentile 20.86 (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.

Summary A race condition in Turbo Frames allows delayed HTTP responses to restore stale session cookies after session-modifying operations. Details Browsers automatically process Set-Cookie headers from HTTP responses. When a Turbo Frame request is in-flight during a session-modifying action (such as logout), the delayed response may include a Set-Cookie header reflecting the session state at request time. This can result in stale session cookies being restored after the session was intentionally modified or invalidated. This condition can occur naturally on slow networks. An active network attacker capable of delaying responses could potentially exploit this to restore previous session state.

Impact Applications using Turbo Frames with cookie-based session storage may experience: - Session state reversion after logout - Unintended restoration of previous authentication state The impact is limited to applications using client-side cookie storage for sessions. Applications using…

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

    Amended from ghsa record GHSA-qppm-g56g-fpvp

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-qppm-g56g-fpvp

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-2025-66803

Advisory: Turbo Frame responses can restore stale session cookies
IDs: CVE-2025-66803, GHSA-qppm-g56g-fpvp
Record: https://patchnext.com/advisories/cve-2025-66803 (revision 3, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @hotwired/turbo 8.0.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @hotwired/turbo: affected <= 8.0.20; fixed in 8.0.21

## Suggested inspection (read-only)
- `npm ls @hotwired/turbo --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 @hotwired/turbo.
- 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-qppm-g56g-fpvp (OSV record GHSA-qppm-g56g-fpvp lists affected ranges: npm @hotwired/turbo >=0 <8.0.21 (fixed))
- Verified: https://github.com/advisories/GHSA-qppm-g56g-fpvp (GitHub-reviewed advisory GHSA-qppm-g56g-fpvp lists affected ranges: npm @hotwired/turbo >=0 <=8.0.20)

Commands are suggestions: review each one before running it.

Loading voting…