Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
GHSA-2586-8ghr-69fj

Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore

Products / packages rails · actionpack

Published

Share

Severity and exploitation

Not in CISA KEVSource: MODERATE

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 04:35:30 UTC
OSV · CVSS:3.0 · 4.2
Assessment vectorCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub_M · CVSS:3.1 · 4.2
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

medium4.2

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Package fixes recorded

Fix versions are recorded for 1 of 1 mapped packages. Check each release branch and any separate product guidance.

What this means

ActionDispatch::Session::CacheStore writes a session back to the cache at the end of each request that loaded it, without checking that the session's cache entry still exists. When a concurrent request destroys the session, through reset_session on logout or by deleting its cache entry on the server, a request that loaded the session earlier and finishes later restores it under its original session ID. Logout and server-side revocation could therefore fail to end a session, and an attacker who holds a stolen session cookie could keep that session valid across the victim's logout.

Source excerpt · OSV

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

rails · GitHub_M

rails

2 ranges
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 8.1, < 8.1.4.1

< 8.0.5.2

unaffected

unknown

Other versions: unknown

Packages

Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.

actionpack RubyGems
Affected range Recorded fix
From 8.1.0.beta1 before 8.1.4.1Ecosystem versions8.1.4.1
Earlier releases before 8.0.5.2Ecosystem versions8.0.5.2

Version evidence: OSV · GHSA-2586-8ghr-69fj

View original version evidence (520 explicit versions)

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

Impact

ActionDispatch::Session::CacheStore writes a session back to the cache at the end of each request that loaded it, without checking that the session's cache entry still exists. When a concurrent request destroys the session, through reset_session on logout or by deleting its cache entry on the server, a request that loaded the session earlier and finishes later restores it under its original session ID. Logout and server-side revocation could therefore fail to end a session, and an attacker who holds a stolen session cookie could keep that session valid across the victim's logout.

Applications that use config.session_store :cache_store are affected, with any cache backend. ActionDispatch::Session::CookieStore is not affected, nor is ActionDispatch::Session::MemCacheStore with Dalli 4.0.0 or later, whose session store does not write back a session that was deleted.

Details

The fixed releases record which session a request loaded and skip the write when that session's cache entry no longer exists. Changes that such a request makes to the destroyed session are discarded, and Rack logs a warning that the session could not be saved. Each request that writes back a session it loaded makes one additional cache read.

Releases

The fixed releases are available at the normal locations.

Patches for those who cannot upgrade at once:

Credit

Found by the team during internal code review.

References

7 sources
rails/rails · security/advisories/GHSA-2586-8ghr-69fj
Security advisoryGitHub_M
rails/rails · commit 5bb5ec6
PatchGitHub_M
rails/rails · commit d479192
PatchGitHub_M
rails/rails · repository
Source reference
rails/rails · releases/tag/v8.0.5.2
Release notesGitHub_M
rails/rails · releases/tag/v8.1.4.1
Release notesGitHub_M
View 1 more references
rubysec/ruby-advisory-db · GHSA-2586-8ghr-69fj.yml
Source reference

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-126076

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-613 ↗

CWE-613: Insufficient Session Expiration

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-11-10
CISA-ADP

Additional data publisher

2026-11-12

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-126076

    Observed 2026-11-12T20:47:21.556Z · upstream updated 2026-11-12T19:05:13.367Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-12T19:04:57.165186Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.