{"id":"CVE-2026-126077","aliases":["GHSA-x6mj-8jx9-qhqv"],"url":"https://o3.security/vulnerability/CVE-2026-126077","summary":"Action Pack: Possible sensitive session information leak in Active Storage proxy mode","details":"### Impact\nWhen `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.\n\nApplications 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](https://github.com/advisories/GHSA-8h22-8cf7-hq6g).\n\n### Details\nIn the fixed releases, a response that skips the session leaves an old-format signed or encrypted cookie unchanged, and the next request that does not skip the session upgrades it. An application that skips the session on every request no longer upgrades its signed or encrypted cookies. Cookies that the application sets explicitly are still written. See the Action Pack CHANGELOG.\n\n### Workarounds\nConfigure caching proxies not to store responses that carry a `Set-Cookie` header, or complete the cookie rotation or serializer migration and remove it from the configuration.\n\n### Releases\nThe fixed releases are available at the normal locations.\n\nPatches for those who cannot upgrade at once:\n- 8.1: https://github.com/rails/rails/commit/849a6c30eacbb6ca4722132f43c4333a93188556.patch\n- 8.0: https://github.com/rails/rails/commit/0e6cf8faa89caf4c64311d35ca2bc88c1458d4e3.patch\n\n### Credit\nThis issue was responsibly reported by HackerOne researcher [flashmyname](https://hackerone.com/flashmyname).","published":"2026-11-10T20:59:00.211Z","modified":"2026-11-12T02:48:34.773430840Z","cvss":{"score":6.8,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N"},"epss":null,"cisaKev":null,"exploitsKnown":null,"affectedPackages":[{"ecosystem":"RubyGems","name":"actionpack","fixedVersion":"8.1.4.1"},{"ecosystem":"RubyGems","name":"actionpack","fixedVersion":"8.0.5.2"}],"fix":{"url":"https://github.com/rails/rails/commit/0e6cf8faa89caf4c64311d35ca2bc88c1458d4e3","label":"rails/rails@0e6cf8f"},"references":[{"type":"WEB","url":"https://github.com/rails/rails/releases/tag/v8.0.5.2"},{"type":"WEB","url":"https://github.com/rails/rails/releases/tag/v8.1.4.1"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/126xxx/CVE-2026-126077.json"},{"type":"ADVISORY","url":"https://github.com/rails/rails/security/advisories/GHSA-x6mj-8jx9-qhqv"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-126077"},{"type":"FIX","url":"https://github.com/rails/rails/commit/0e6cf8faa89caf4c64311d35ca2bc88c1458d4e3"},{"type":"FIX","url":"https://github.com/rails/rails/commit/849a6c30eacbb6ca4722132f43c4333a93188556"},{"type":"PACKAGE","url":"https://github.com/rails/rails"},{"type":"WEB","url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/GHSA-x6mj-8jx9-qhqv.yml"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-11-12T02:48:34.773430840Z"}}