rack-session up to 2.1.0 Session Cookie Rack::Session::Pool race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in rack-session up to 2.1.0. Affected is the function Rack::Session::Pool of the component Session Cookie Handler. Performing a manipulation results in race condition.
This vulnerability is cataloged as CVE-2025-46336. The attack must originate from the local network. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in rack-session up to 2.1.0. This affects the function Rack::Session::Pool of the component Session Cookie Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-46336 since 04/23/2025. The exploitability is told to be difficult. The attack needs to be initiated within the local network. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 252910 (Linux Distros Unpatched Vulnerability : CVE-2025-46336), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.1.1 eliminates this vulnerability. Applying the patch c28c4a8c1861d814e09f2ae48264ac4c40be2d3b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (252910). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.2
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 252910
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-46336
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: rack-session 2.1.1
Patch: c28c4a8c1861d814e09f2ae48264ac4c40be2d3b
Timeline
04/23/2025 🔍05/09/2025 🔍
05/09/2025 🔍
08/20/2025 🔍
Sources
Advisory: GHSA-9j94-67jr-4cqjStatus: Confirmed
CVE: CVE-2025-46336 (🔍)
GCVE (CVE): GCVE-0-2025-46336
GCVE (VulDB): GCVE-100-308109
Entry
Created: 05/09/2025 07:06Updated: 08/20/2025 22:45
Changes: 05/09/2025 07:06 (66), 08/20/2025 22:45 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.