CVE-2026-126067: Action Pack: Missing SameSite attribute on session cookies from Action Pack session stores
Impact Action Pack session stores other than ActionDispatch::Session::CookieStore (CacheStore, MemCacheStore, and third-party stores built on AbstractStore, AbstractSecureStore or the session mixins) write the session cookie without a SameSite attribute, regardless of config.actiondispatch.cookiessamesiteprotection, which defaults to :lax. Only CookieStore applies the configured policy.
Published Nov 10, 2026
Affected packages
actionpack
- Ecosystem
- RubyGems
- Affected
- >= 8.1.0.beta1, < 8.1.4.1
- Fixed in
- 8.1.4.1
- Check
bundle info actionpack
actionpack
- Ecosystem
- RubyGems
- Affected
- < 8.0.5.2
- Fixed in
- 8.0.5.2
- Check
bundle info actionpack
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Action Pack session stores other than ActionDispatch::Session::CookieStore (CacheStore, MemCacheStore, and third-party stores built on AbstractStore, AbstractSecureStore or the session mixins) write the session cookie without a SameSite attribute, regardless of config.action_dispatch.cookies_same_site_protection, which defaults to :lax. Only CookieStore applies the configured policy. In browsers that do not treat a cookie without the attribute as SameSite=Lax, a cross-site request could carry the session cookie, possibly leading to cross-site request forgery against actions that do not verify an authenticity token, such as those of API-only applications.
Applications are affected when they use a session store other than CookieStore and do not pass same_site: to config.session_store.
Details
In the fixed releases, every session store sets the session cookie's SameSite attribute from cookies_same_site_protection when its options have no :same_site key. An explicit same_site: option, including same_site: nil, and a :same_site value in a store's DEFAULT_OPTIONS still take precedence.
Workarounds
Pass same_site: when configuring the session store, for example config.session_store :cache_store, same_site: :lax.
Releases
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
- 8.1: https://github.com/rails/rails/commit/2d9f502df941e31ce9bad0e846564f49396bed46.patch
- 8.0: https://github.com/rails/rails/commit/f2392996be723708271a8d30bfcf0edc221e53ef.patch
Credit
This issue was responsibly reported by HackerOne researcher tjvc.
References
- https://github.com/rails/rails/security/advisories/GHSA-gmj8-hvj3-49mw
- https://github.com/rails/rails/commit/2d9f502df941e31ce9bad0e846564f49396bed46
- https://github.com/rails/rails/commit/f2392996be723708271a8d30bfcf0edc221e53ef
- https://github.com/rails/rails/releases/tag/v8.0.5.2
- https://github.com/rails/rails/releases/tag/v8.1.4.1
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/GHSA-gmj8-hvj3-49mw.yml
- https://github.com/advisories/GHSA-gmj8-hvj3-49mw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-126072
Action Pack: Possible DoS vulnerability in Action Controller Live streaming
medium5.9Nov 12, 2026CVE-2026-126077
Action Pack: Possible sensitive session information leak in Active Storage proxy mode
medium6.8Nov 12, 2026CVE-2026-126081
Action Pack: Possible Strong Parameters Bypass in Parameters#each_key
high7.5Nov 12, 2026CVE-2026-126073
Action Pack: Possible cache poisoning in Action Pack content negotiation
medium4.8Nov 10, 2026CVE-2026-126076
Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore
medium4.2Nov 10, 2026CVE-2026-126083
Action Pack: Possible IP spoofing in Action Dispatch RemoteIp
high7.4Nov 10, 2026
