GHSA-QPPM-G56G-FPVP
Vulnerability from github – Published: 2026-01-20 18:58 – Updated: 2026-01-21 21:11Summary
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 server-side session stores (Redis, database, etc.) are not meaningfully affected, as the server-side session state remains authoritative.
Patches
Upgrade to Turbo 8.0.21 or later. The fix cancels in-flight Turbo Frame requests when: - The frame element is disconnected from the DOM - The frame's disabled attribute is set - The frame's src attribute is cleared
Workarounds
- Use server-side session storage instead of a cookie store like Rails's cookie store
- Ensure logout flows remove or disable Turbo Frame elements before invalidating sessions
References
- https://github.com/hotwired/turbo/pull/1399
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 8.0.20"
},
"package": {
"ecosystem": "npm",
"name": "@hotwired/turbo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.21"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-66803"
],
"database_specific": {
"cwe_ids": [
"CWE-362",
"CWE-367",
"CWE-613"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-20T18:58:15Z",
"nvd_published_at": "2026-01-20T19:15:49Z",
"severity": "LOW"
},
"details": "### Summary\nA race condition in Turbo Frames allows delayed HTTP responses to restore stale session cookies after session-modifying operations.\n\n### Details\nBrowsers 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.\n\nThis condition can occur naturally on slow networks. An active network attacker capable of delaying responses could potentially exploit this to restore previous session state.\n\n ### Impact\n Applications using Turbo Frames with cookie-based session storage may experience:\n - Session state reversion after logout\n - Unintended restoration of previous authentication state\n\nThe impact is limited to applications using client-side cookie storage for sessions. Applications using server-side session stores (Redis, database, etc.) are not meaningfully affected, as the server-side session state remains authoritative.\n\n### Patches\n Upgrade to Turbo 8.0.21 or later. The fix cancels in-flight Turbo Frame requests when:\n - The frame element is disconnected from the DOM\n - The frame\u0027s disabled attribute is set\n - The frame\u0027s src attribute is cleared\n\n### Workarounds\n - Use server-side session storage instead of a cookie store like Rails\u0027s cookie store\n - Ensure logout flows remove or disable Turbo Frame elements before invalidating sessions\n\n### References\n - https://github.com/hotwired/turbo/pull/1399",
"id": "GHSA-qppm-g56g-fpvp",
"modified": "2026-01-21T21:11:06Z",
"published": "2026-01-20T18:58:15Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/hotwired/turbo/security/advisories/GHSA-qppm-g56g-fpvp"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66803"
},
{
"type": "WEB",
"url": "https://github.com/hotwired/turbo/pull/1399"
},
{
"type": "WEB",
"url": "https://github.com/hotwired/turbo/commit/899df356e9f4b3303cca217cd14b3f846edda10d"
},
{
"type": "PACKAGE",
"url": "https://github.com/hotwired/turbo"
},
{
"type": "WEB",
"url": "https://github.com/hotwired/turbo/releases/tag/v8.0.21"
},
{
"type": "WEB",
"url": "https://turbo.hotwired.dev/handbook/frames"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "Turbo Frame responses can restore stale session cookies"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.