CVE-2025-64100: CKAN vulnerable to fixed session IDs
Impact Session ids could be fixed by an attacker if the site is configured with server-side session storage (CKAN uses cookie-based session storage by default). The attacker would need to either set a cookie on the victim's browser or steal the victim's currently valid session. Session identifiers are now regenerated after each login.
Published Oct 29, 2025
Affected packages
ckan
- Ecosystem
- PyPI
- Affected
- >= 2.10.0, < 2.10.9
- Fixed in
- 2.10.9
- Check
pip show ckan
ckan
- Ecosystem
- PyPI
- Affected
- >= 2.11.0, < 2.11.4
- Fixed in
- 2.11.4
- Check
pip show ckan
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Session ids could be fixed by an attacker if the site is configured with server-side session storage (CKAN uses cookie-based session storage by default). The attacker would need to either set a cookie on the victim's browser or steal the victim's currently valid session. Session identifiers are now regenerated after each login.
Patches
This vulnerability has been fixed in CKAN 2.10.9 and 2.11.4
References
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-104773
CKAN: Session Fixation in Registration View
medium6.8Nov 20, 2026CVE-2026-42032
CKAN has Unauthenticated Authorization Bypass in `datastore_search_sql`
medium6.7Apr 30, 2026CVE-2026-41132
CKAN has no certificate validation on STMP connection
medium6.6Apr 29, 2026CVE-2026-41255
CKAN has CSRF exemption primed by anonymous requests
medium6.1Apr 29, 2026CVE-2026-42031
CKAN has Unauthenticated SQL Injection and Authorization Bypass in `datastore_search_sql`
high8.3Apr 29, 2026CVE-2025-54384
CKAN vulnerable to stored XSS in resource description
medium6.3Oct 29, 2025
