Quick answers
- Is CVE-2026-41255 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41255 being exploited in the wild.
- How severe is CVE-2026-41255?
- Medium severity, with a CVSS score of 6.1, published 13 May 2026.
- Which products and versions are affected?
- CKAN < 2.10.10, < 2.11.5; ckan (PyPI) ECOSYSTEM:introduced=2.10.0,fixed=2.10.10, ECOSYSTEM:introduced=2.10.0,fixed=2.10.10,introduced=2.11.0,fixed=2.11.5.
- Is there a fix for CVE-2026-41255?
- Yes. ckan (PyPI): upgrade to 2.10.10, 2.11.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41255 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41255?
- 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.10.10, 2.11.5 or later
pip install "ckan>=2.11.5"
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in CKAN due to improper state management in the flask-wtf.csrf.CSRFProtect() middleware. When an endpoint is accessed via an unauthenticated request or a request using tokens, the middleware incorrectly marks the view as exempt from CSRF protection. This exemption is stored in a module-level variable within the flask_app middleware, causing the exemption to persist for the entire life of the server process (e.g., a uwsgi worker). An attacker can 'prime' a worker by sending an anonymous request to a protected endpoint, subsequently allowing them to bypass CSRF protections for authenticated users handled by that same worker. This can be combined with XSS or social engineering to execute unauthorized actions using a victim's credentials. The issue is fixed in versions 2.10.10 and 2.11.5.
Affected products
- ckan ckan >= 2.10.0, < 2.10.10; >= 2.11.0, <= 2.11.4
Identifiers
- CVE-2026-41255
- GHSA-mcvf-jxcw-vj73
- PYSEC-2026-2418
Timeline
- 2026-04-29: disclosed
- 2026-04-29: advisory
- 2026-04-29: patched