CVE-2025-46336: Rack session Rack Session Gets Restored After Vulnerability

MODERATE
Advisory Identifier: GHSA-9j94-67jr-4cqj
CVSS 4.2
CWE-613 CWE-362 CWE-367
Published
Advisory Summary

CVE-2025-46336 is a MODERATE (CVSS 4.2) rack session gets restored after vulnerability (CWE-613: Insufficient Session Expiration) affecting Rack session libraries in the RubyGems ecosystem. The issue involves rack session gets restored after deletion. Remediation is available by upgrading affected packages to version 2.1.1.

CVE-2025-46336 at a Glance

CVE Identifier CVE-2025-46336
GHSA Identifier GHSA-9j94-67jr-4cqj
Severity MODERATE
CVSS v3.1 Base Score 4.2
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product Rack session
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 4.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-46336

To remediate this vulnerability, upgrade all affected Rack session dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

rack-session fixed: 2.1.1
Upgrade rack-session to 2.1.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for rack-session

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-46336, inspect your project dependencies for Rack session:

inspect dependencies for rack-session

Analyze the terminal output to locate any version of Rack session in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Rack session, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary When using the `Rack::Session::Pool` middleware, simultaneous rack requests can restore a deleted rack session, which allows the unauthenticated user to occupy that session. ## Details [Rack session middleware](https://github.com/rack/rack-session/blob/v2.1.0/lib/rack/session/abstract/id.rb#L271-L278) prepares the session at the beginning of request, then saves is back to the store with possible changes applied by host rack application. This way the session becomes to be a subject of race conditions in general sense over concurrent rack requests. ## Impact 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. ## Mitigation - Update to the latest version of `rack-session`, or - Ensure your application invalidates sessions atomically by marking them as logged out e.g., using a `logged_out` flag, instead of deleting them, and check this flag on every request to prevent reuse, or - Implement a custom session store that tracks session invalidation timestamps and refuses to accept session data if the session was invalidated after the request began. ## Related This code was previously part of `rack` in Rack < 3, see <https://github.com/rack/rack/security/advisories/GHSA-vpfw-47h7-xj4g> for the equivalent advisory in `rack` (affecting Rack < 3 only).

CVE-2025-46336 Affected Rack session Versions

1 component(s)
Fixed Versions:
2.1.1
Product / Package Ecosystem Affected Versions Fixed Version
rack-session
RubyGems
≥ 2.0.0
< 2.1.1
2.1.1

References

Frequently Asked Questions

What is CVE-2025-46336?
CVE-2025-46336 is a security vulnerability in Rack session involving Rack session gets restored after deletion under CWE-613: Insufficient Session Expiration.
Which Rack session versions are affected?
Affected versions include releases prior to 2.1.1 across affected packages: rack-session.
What version fixes CVE-2025-46336?
Upgrading to 2.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is rack-session affected?
Yes, rack-session is affected in releases prior to 2.1.1. Upgrade your dependency to 2.1.1 or later.
What is the CVSS score of CVE-2025-46336?
CVE-2025-46336 has a CVSS v3.1 base score of 4.2 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2025-46336?
CVE-2025-46336 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check RubyGems dependencies for CVE-2025-46336?
Run the dependency tree command: 'inspect dependencies for rack-session'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9j94-67jr-4cqj",
  "modified" : "2025-05-09T14:34:48Z",
  "published" : "2025-05-08T14:45:33Z",
  "aliases" : [ "CVE-2025-46336" ],
  "summary" : "Rack session gets restored after deletion",
  "details" : "## Summary\n\nWhen using the `Rack::Session::Pool` middleware, simultaneous rack requests can restore a deleted rack session, which allows the unauthenticated user to occupy that session.\n\n## Details\n\n[Rack session middleware](https://github.com/rack/rack-session/blob/v2.1.0/lib/rack/session/abstract/id.rb#L271-L278) prepares the session at the beginning of request, then saves is back to the store with possible changes applied by host rack application. This way the session becomes to be a subject of race conditions in general sense over concurrent rack requests.\n\n## Impact\n\nWhen 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.\n\n## Mitigation\n\n- Update to the latest version of `rack-session`, or\n- Ensure your application invalidates sessions atomically by marking them as logged out e.g., using a `logged_out` flag, instead of deleting them, and check this flag on every request to prevent reuse, or\n- Implement a custom session store that tracks session invalidation timestamps and refuses to accept session data if the session was invalidated after the request began.\n\n## Related\n\nThis code was previously part of `rack` in Rack < 3, see <https://github.com/rack/rack/security/advisories/GHSA-vpfw-47h7-xj4g> for the equivalent advisory in `rack` (affecting Rack < 3 only).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "rack-session"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rack/rack-session/security/advisories/GHSA-9j94-67jr-4cqj"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rack/rack/security/advisories/GHSA-vpfw-47h7-xj4g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-46336"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rack/rack-session/commit/c28c4a8c1861d814e09f2ae48264ac4c40be2d3b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rack/rack-session"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack-session/CVE-2025-46336.yml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362", "CWE-367", "CWE-613" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-05-08T14:45:33Z",
    "nvd_published_at" : "2025-05-08T20:15:30Z"
  }
}