Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRequest Active Storage proxy URL with old-format cookie
-
DeliverySession cookie re-upgraded into Set-Cookie on cacheable response
-
ExploitShared cache stores response with Set-Cookie
-
ExecutionLater user served cached Set-Cookie
-
ImpactVictim inherits leaked/attacker session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires ALL of: (1) the application serves Active Storage files through the proxy controllers (ActiveStorage::Proxy, which rely on ActiveStorage::DisableSession / request.session_options[:skip]); (2) a cookie rotation is configured via config.action_dispatch.cookies_rotations, OR a :hybrid cookie serializer migration is in progress, so that incoming signed/encrypted cookies are in an old format that triggers a re-upgrade write; and (3) the app runs behind a shared/caching proxy that stores responses together with their Set-Cookie header on public responses. A victim request carrying an old-format session cookie (UI:R) is needed to seed the cached Set-Cookie. Limiting factors: if rotations/migrations are not configured, or the cache strips/does not store Set-Cookie on public responses, the condition cannot occur; cookies the application sets explicitly are still written normally, and completing or removing the rotation/serializer migration eliminates the trigger. Vendor workaround: configure caching proxies not to store responses carrying Set-Cookie, or finish and remove the rotation/serializer migration; the complete fix is upgrading to 8.1.4.1 or 8.0.5.2. |
| Impact | This is a genuine but narrowly-scoped information-disclosure flaw (CWE-200) in Rails Action Pack, rated CVSS 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N). The network vector and PR:N look alarming, but the real-world risk is gated hard by AC:H and UI:R and by a specific multi-condition deployment: the app must serve Active Storage files through the proxy controllers, must have a cookie rotation (config.action_dispatch.cookies_rotations) OR a :hybrid serializer migration configured, AND must sit behind a shared cache that stores Set-Cookie on public responses. All three must hold simultaneously, so most Rails deployments are not exposed. No EPSS score was supplied and the CVE is not in CISA KEV, so there is no active-exploitation signal; status is 'no public exploit identified at time of analysis' (reported responsibly via GitHub/HackerOne by researcher flashmyname, with no weaponized PoC in the input). The vendor priority label is this_month, consistent with a serious-but-conditional session-leak rather than an emergency. Net: this is a real priority for the specific population running Active Storage proxy mode with rotations behind a caching proxy that caches Set-Cookie - for them it can cause cross-user session hijacking - but it is low real-world risk for the broad Rails base that does not meet all the preconditions. It is explicitly a bypass of the earlier fix for CVE-2024-26144. Note the apparent tension to verify: PR:N implies no authentication, yet the impactful outcome depends on a victim's valid session cookie being rewritten and then cached, and UI:R reflects that a legitimate user's request is needed to seed the cached response. |
| Exploit ScenarioDerived | A legitimate user with an old-format (rotated-secret or pre-:hybrid) session cookie requests an Active Storage file through the proxy controller; Action Pack re-upgrades and writes the session cookie into Set-Cookie on that public, cacheable response, and the shared cache stores it against the URL. A later user requesting the same cached URL is served the first user's Set-Cookie and inherits their session, or an attacker who deliberately seeds the cache with their own session cookie has it handed to subsequent victims. No public exploit code is identified; exploitation requires the vulnerable configuration (Active Storage proxy + cookie rotation/:hybrid migration + a cache that stores Set-Cookie) and AC:H/UI:R conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 11, 2026
Rails Action Pack (ActionDispatch::Cookies) writes upgraded signed and encrypted cookies back into responses even when the request was flagged to skip the session, so Active Storage proxy responses that are meant to be public and cacheable can still carry a session cookie in Set-Cookie. Applications are affected only when they serve Active Storage files through the proxy controllers, have a cookie rotation (config.action_dispatch.cookies_rotations) or a :hybrid serializer migration configured, and sit behind a shared cache that stores Set-Cookie on public responses; such a cache could then hand one user's session to later requesters of the same URL, or serve an attacker's session to other users. Rated CVSS 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N), the flaw requires a victim request carrying an old-format session cookie to seed the cached header, and no public exploit was identified at time of analysis; this is a path around the fix for CVE-2024-26144.
RemediationAI
Vendor-released patch: upgrade to Action Pack 8.1.4.1 (Rails 8.1 branch) or 8.0.5.2 (Rails 8.0 branch); both releases are available at https://github.com/rails/rails/releases/tag/v8.1.4.1 and https://github.com/rails/rails/releases/tag/v8.0.5.2. Deployments that cannot upgrade immediately can apply the vendor-supplied patches, 8.1: https://github.com/rails/rails/commit/849a6c30eacbb6ca4722132f43c4333a93188556.patch and 8.0: https://github.com/rails/rails/commit/0e6cf8faa89caf4c64311d35ca2bc88c1458d4e3.patch. The vendor-listed workarounds are to configure caching proxies so they do not store responses that carry a Set-Cookie header, or to complete the cookie rotation or serializer migration and remove it from the configuration so no old-format cookies trigger a re-upgrade write. Be aware of the behavioural side effect of the fix: a response that skips the session now leaves an old-format signed or encrypted cookie unchanged and defers the upgrade to the next request that does not skip the session, so an application that skips the session on every request will no longer upgrade its signed or encrypted cookies, while cookies the application sets explicitly are still written. Full details are in the advisory at https://github.com/rails/rails/security/advisories/GHSA-x6mj-8jx9-qhqv.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in rubygems, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Action Pack's ActionDispatch::Cookies middleware verifies signed cookies with ActiveSupport::MessageVerifier and decrypts encrypted cookies with ActiveSupport::MessageEncryptor. When an incoming cookie was produced under an older secret still listed in config.action_dispatch.cookies_rotations, or was serialized in the Marshal format that a :hybrid cookie serializer migrates away from, the middleware transparently re-serializes it into the current format and writes it back to the response. The commit adds an @upgraded_cookies tracking set and suppresses that re-write when request.session_options[:skip] is set - a flag ActionStorage::DisableSession sets so that the public, immutable Active Storage proxy responses never emit a session cookie. Because those proxy controllers still load the session, a request arriving with an old-format session cookie received the rewritten cookie on a cacheable response. The root cause is CWE-200 (Exposure of Sensitive Information), realized here as a cache-level session disclosure rather than a direct read. The parse logic in the encrypted/signed jar now records upgraded cookie names, and the response-building path skips them when the session is skipped; explicitly set cookies are still written, and a later request that does not skip the session performs the upgrade. Exploitation depends on the three-way confluence described in the vendor advisory and is inherently high-complexity (AC:H) and victim-interaction dependent (UI:R), and the CVSS vector shows PR:N, so no authentication is required of the attacker.
Know when Ruby On Rails gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Network-reachable but AC:H due to the multi-condition config (proxy + rotation + caching Set-Cookie) and UI:R needing a victim request; stolen session yields confidentiality and impersonation impact (C:H/I:H), no availability effect.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
Action Pack is a framework for handling and responding to web requests. Prior to 8.1.4.1 and 8.0.5.2, When ActionDispatch::Cookies reads a signed or encrypted cookie that was written under a rotated secret (config.action_dispatch.cookies_rotations) or in the format that a :hybrid cookie serializer migrates from, it writes the cookie back to the response in the current format, and that write ignores request.session_options[:skip]. ActiveStorage::DisableSession relies on that option to keep the session cookie off the public, immutable responses of the Active Storage proxy controllers, but those controllers still load the session, so a request carrying an old-format session cookie could receive the rewritten session cookie in Set-Cookie on a cacheable response. A shared cache that stores such a response together with its Set-Cookie header could then serve one user's session to later requesters of the same URL, or serve an attacker's session to other users. Applications are affected when they serve Active Storage files through the proxy controllers, have a cookie rotation or a :hybrid serializer migration configured, and run behind a cache that stores Set-Cookie on public responses. This is a path around the fix for CVE-2024-26144. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Ruby On Rails
View alllib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly
active_support/core_ext/hash/conversions.rb in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, an
Action Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1.14.2, and 4.2.x before 4.2.5.2 allows remote attackers to e
actionpack/lib/action_view/lookup_context.rb in Action View in Ruby on Rails 3.x before 3.2.16 and 4.x before 4.0.2 allo
Unauthenticated attackers can write arbitrary files on a Ruby on Rails host and, when Active Storage uses the Disk servi
Unauthenticated remote code execution is achievable in Square Squash (all versions through commit e73f280) through a two
SQL injection vulnerability in the 'order' method in Ruby on Rails 5.1.4 and earlier allows remote attackers to execute
SQL injection vulnerability in the 'reorder' method in Ruby on Rails 5.1.4 and earlier allows remote attackers to execut
SQL injection vulnerability in the Active Record component in Ruby on Rails before 3.0.18, 3.1.x before 3.1.9, and 3.2.x
The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly
ActiveRecord in Ruby on Rails before 2.3.17 and 3.x before 3.1.0 allows remote attackers to cause a denial of service or
Authenticated store customers can seize other shoppers' guest carts in Spree Commerce by calling PATCH /api/v3/store/car
EUVD-2026-122926
GHSA-x6mj-8jx9-qhqv
NVD
CVE.org
EPSS
VulDB
Exploit-DB