GHSA-4cx3-3c38-j9vv
katalyst-koi: Session cookies can be replayed after user logout
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| RubyGems | katalyst-koi | < 4.20.0 | 4.20.0 |
| RubyGems | katalyst-koi | >= 5.0.0, < 5.6.0 | 5.6.0 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
Admin session cookies were not invalidated when an admin user logged out. An attacker with access to a valid admin session cookie could continue to access admin functionality after logout, until the cookie expired or session secrets were rotated.
This affects applications using Koi admin authentication where an admin session cookie may have been exposed, cached, intercepted, or otherwise retained after logout.
### Patches
The issue has been patched by recording admin logout time and rejecting any admin session cookie created before the user’s most recent logout.
Users should upgrade to the patched Koi releases once available.
### Workarounds
Katalyst Koi recommends upgrading to the latest available version, or back porting the changes released in 5.6.0/4.20.0
### Resources
This is an application of https://guides.rubyonrails.org/v5.2.0/security.html#replay-attacks-for-cookiestore-sessions
References
External links from the advisory. They lead to third-party sites.
- https://github.com/katalyst/koi/security/advisories/GHSA-4cx3-3c38-j9vv
- https://nvd.nist.gov/vuln/detail/CVE-2026-44511
- https://github.com/katalyst/koi
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/katalyst-koi/CVE-2026-44511.yml
- https://guides.rubyonrails.org/v5.2.0/security.html#replay-attacks-for-cookiestore-sessions