Rack Session
Approved changes feed: RSS · Atom
cpe:2.3:a:rack:rack-session:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Rack (5b83186e-2c4c-5047-aba1-e2d157c9b630) |
|---|---|
| Product | Rack Session (e05c93bb-7186-5bf6-80ae-b24ee7969606) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:gem/rack-session |
purl2cpe | 2026-06-01 10:12:58.782680 |
pkg:github/rack/rack-session |
purl2cpe | 2026-06-01 10:12:58.782683 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-39324 |
vulnerable | 2026-06-08 08:01:16.189146 |
Rack::Session::Cookie secrets: decrypt failure fallback enables secretless session forgery and Marshal deserialization
Rack::Session is a session management implementation for Rack. From 2.0.0 to before 2.1.2, Rack::Session::Cookie incorrectly handles decryption failures when configured with secrets:. If cookie decryption fails, the implementation falls back to a default decoder instead of rejecting the cookie. This allows an unauthenticated attacker to supply a crafted session cookie that is accepted as valid session data without knowledge of any configured secret. Because this mechanism is used to load session state, an attacker can manipulate session contents and potentially gain unauthorized access. This vulnerability is fixed in 2.1.2.
Published: 2026-04-07T18:13:28.639Z
Updated: 2026-04-08T18:44:07.145Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-46336 |
vulnerable | 2026-06-08 07:27:08.078071 |
Rack session gets restored after deletion
MEDIUM (4.2)
Rack::Session is a session management implementation for Rack. In versions starting from 2.0.0 to before 2.1.1, when using the Rack::Session::Pool middleware, and provided the attacker can acquire a session cookie (already a major issue), the session may be restored if the attacker can trigger a long running request (within that same session) adjacent to the user logging out, in order to retain illicit access even after a user has attempted to logout. This issue has been patched in version 2.1.1.
Published: 2025-05-08T19:26:01.638Z
Updated: 2025-05-08T20:18:38.555Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.