In short
- CVE-2026-41255 is a MEDIUM (CVSS 6.1) vulnerability affecting ckan, ckan (okfn).
- Chance of exploitation in the next 30 days (EPSS): 0.12%, higher than 2.1% of all vulnerabilities.
- Fix: update to 2.10.10, 2.11.5 or later.
| Package | Affected versions | Patched versions |
|---|
| ckan PyPI | ≥ 2.10.0, < 2.10.10≥ 2.11.0, < 2.11.5
| 2.10.102.11.5
|
| ckan | ≥ 2.11.0, < 2.11.5< 2.10.10
| 2.11.52.10.10
|
Description
Views can be marked as exempt from CSRF protection
Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection.
The marking was a member variable in flask-wtf.csrf.CSRFProtect(), which was stored as a module level variable in the flask_app middleware. Thsi API was never intended for request level changes, it is primarily a decorator for static configuration.
An unauthenticated request could hit a protected endpoint, exempting it from CSRF protection for the life of the particular server process. (e.g. one worker of uwsgi).
This could be leveraged with XSS to perform actions using other user's credentials.
References
NVD description
CKAN is an open-source DMS (data management system) for powering data hubs and data portals. Prior to 2.10.10 and 2.11.5, Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection. The marking was a member variable in flask-wtf.csrf.CSRFProtect(), which was stored as a module level variable in the flask_app middleware. This API was never intended for request level changes, it is primarily a decorator for static configuration. An unauthenticated request could hit a protected endpoint, exempting it from CSRF protection for the life of the particular server process. (e.g. one worker of uwsgi). This vulnerability is fixed in 2.10.10 and 2.11.5.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free