Quick answers
- Is CVE-2025-64100 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-64100 being exploited in the wild.
- How severe is CVE-2025-64100?
- Medium severity, with a CVSS score of 6.1, published 29 October 2025.
- Which products and versions are affected?
- CKAN 2.10.0 through 2.10.8, 2.11.0 through 2.11.3; ckan (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.9,introduced=2.11.0,fixed=2.11.4.
- Is there a fix for CVE-2025-64100?
- Yes. ckan (PyPI): upgrade to 2.11.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-64100 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-64100?
- Check whether you run CKAN or ckan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ckan (PyPI): upgrade to 2.11.4 or later
pip install "ckan>=2.11.4"
Technical details
This is a session fixation vulnerability (CWE-384) in CKAN's session management. The vulnerability exists when CKAN is configured with server-side session storage (though the default is cookie-based). An attacker can fix a session ID by either setting a cookie on the victim's browser or stealing a currently valid session token. The attacker then waits for the victim to log in, at which point the pre-determined session ID remains in use, allowing the attacker to use that same session to access the victim's account. The fix involves regenerating session identifiers after each login. This has been patched in CKAN 2.10.9 and 2.11.4.
Affected products
- CKAN CKAN 2.10.0 through 2.10.8, 2.11.0 through 2.11.3
Identifiers
- CVE-2025-64100
- GHSA-2hvh-cw5c-8q8q
- PYSEC-2026-1246
Timeline
- 2025-10-29: disclosed
- 2025-10-29: patched: Patched in CKAN 2.10.9 and 2.11.4