CVE-2025-46336 | Rack session gets restored after deletion

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-08 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-46336 is rated Low Risk (27.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.11%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-46336

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 0.02% 0.11% +0.09%
2 2025-05-09 0.02%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-46336

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.6 2.5 [email protected]

Weakness enumeration for CVE-2025-46336

GitHub Security Advisory for CVE-2025-46336

GHSA-9j94-67jr-4cqj · Severity: medium · Ecosystem: rubygems — Rack session gets restored after deletion

OS Trackers for CVE-2025-46336

vendor priority summary link
debian not yet assigned CVE-2025-46336 not yet assigned priority: Debian including 1 source packages (ruby-rack-session), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2025-46336
redhat medium https://access.redhat.com/security/cve/CVE-2025-46336
suse medium CVE-2025-46336 severity moderate: SUSE including 1 source package names (ruby3.4-rubygem-rack-session-2.1.1-1.1), 1 product×package rows across 1 product lines (openSUSE Tumbleweed): Fixed 1. https://www.suse.com/security/cve/CVE-2025-46336/
ubuntu medium CVE-2025-46336 medium priority: Ubuntu including 1 source packages (ruby-rack-session), 1 status rows across 1 suites (upstream): released 1. https://ubuntu.com/security/CVE-2025-46336

Affected software / configurations for CVE-2025-46336

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-46336

cvelogic Threat Intelligence