Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-32441: Rack session gets restored after deletion

Noroxi assessment

Priority: Monitor (action score 16/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: ruby-rack (Debian:11) 2.1.4-3+deb11u4; ruby-rack (Debian:12) 2.2.20-0+deb12u1; ruby-rack (Debian:13) 3.0.8-2.

Low priority for now. Upgrade to ruby-rack (Debian:11) 2.1.4-3+deb11u4; ruby-rack (Debian:12) 2.2.20-0+deb12u1; ruby-rack (Debian:13) 3.0.8-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Rack is a modular Ruby web server interface. Prior to version 2.2.14, 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. Rack session middleware 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. 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. Version 2.2.14 contains a patch for the issue. Some other mitigations are available. Either ensure the 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.

MediumCVSS 4.2 · v3.1—No exploit Fix available
Published
May 7, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.2
CNA · GitHub_M
4.2
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-32441

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for rack records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
rackrack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • rack rackbefore 2.2.14

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • rack rack

    • < 2.2.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11ruby-rackbefore 2.1.4-3+deb11u42.1.4-3+deb11u4
Debian:12ruby-rackbefore 2.2.20-0+deb12u12.2.20-0+deb12u1
Debian:13ruby-rackbefore 3.0.8-23.0.8-2
openSUSE:Leap 15.6rmt-serverbefore 2.23-150500.3.34.22.23-150500.3.34.2
openSUSE:Leap 15.6rubygem-rackbefore 2.0.8-150000.3.31.12.0.8-150000.3.31.1
RubyGemsrackbefore 2.2.142.2.14
SUSE:Linux Enterprise High Availability Extension 15 SP3rubygem-rackbefore 2.0.8-150000.3.31.12.0.8-150000.3.31.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP3rmt-serverbefore 2.23-150300.3.54.12.23-150300.3.54.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP4rmt-serverbefore 2.23-150400.3.42.12.23-150400.3.42.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP5rmt-serverbefore 2.23-150500.3.34.22.23-150500.3.34.2
SUSE:Linux Enterprise Module for Public Cloud 15 SP7rmt-serverbefore 2.23-150700.3.6.12.23-150700.3.6.1

Same product

rack: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-25126Rack ReDos in content type parsing (2nd degree polynomial)
    41Plan
  • CVE-2024-26146Possible Denial of Service Vulnerability in Rack Header Parsing
    31Monitor
  • CVE-2023-27530A DoS vulnerability exists in Rack <v3.0.4.2, <v2.2.6.3, <v2.1.4.3 and <v2.0.9.3 within in the Multipart MIME parsing code in which could al
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-27111Mar 4, 2025 · Escape Sequence Injection vulnerability in Rack lead to Possible Log Injection
    27Monitor
  • ← EarlierCVE-2025-27610Mar 10, 2025 · Local File Inclusion in Rack::Static
    30Monitor
  • Later →CVE-2025-46727May 7, 2025 · Unbounded-Parameter DoS in Rack::QueryParser
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-rack2.2.20-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:rmt-server2.23-150500.3.34.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:rubygem-rack2.0.8-150000.3.31.1 · openSUSE:Leap 15.6Package registry (OSV)
RubyGems:rack2.2.14Package registry (OSV)
suse:rmt-server2.23-150400.3.42.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4Package registry (OSV)
suse:rmt-server2.23-150500.3.34.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:rubygem-rack2.0.8-150000.3.31.1 · SUSE:Linux Enterprise High Availability Extension 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records