Activerecord-session_store Vulnerable to Timing Attack
CVE-2019-25025GHSA-cvw2-xj8r-mjf7
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (activerecord-session_store 2.0.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
RubyGems activerecord-session_store
- Affected
- <= 1.1.3
- Fixed in
- 2.0.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cvw2-xj8r-mjf7 lists affected ranges: RubyGems activerecord-session_store >=0 <=1.1.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2019-25025: 1.84% estimated exploitation activity in the next 30 days; percentile 78.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
The activerecord-sessionstore (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782. Recommendation This has been fixed in version 2.0.0. All users are advised to update to this version or later.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-cvw2-xj8r-mjf7
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2019-25025 Advisory: Activerecord-session_store Vulnerable to Timing Attack IDs: CVE-2019-25025, GHSA-cvw2-xj8r-mjf7 Record: https://patchnext.com/advisories/cve-2019-25025 (revision 1, source checked 26 Oct 2026, 15:47 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: activerecord-session_store 2.0.0. A vendor fix does not mean a deployment is fixed. ## Affected components - RubyGems activerecord-session_store: affected <= 1.1.3; fixed in 2.0.0 ## Suggested inspection (read-only) - RubyGems activerecord-session_store: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on activerecord-session_store. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-cvw2-xj8r-mjf7 (GitHub-reviewed advisory GHSA-cvw2-xj8r-mjf7 lists affected ranges: RubyGems activerecord-session_store >=0 <=1.1.3) Commands are suggestions: review each one before running it.
Loading voting…