CKAN has CSRF exemption primed by anonymous requests
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 * [Vulnerability report](https://github.com/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255) by @Shirshaw64p (original reporter)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-41255US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://docs.ckan.org/en/2.10/changelog.html#v-2-10-10-2026-04-29WEB
- https://docs.ckan.org/en/2.11/changelog.html#v-2-11-5-2026-04-29WEB
- https://github.com/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255WEB
- https://github.com/ckan/ckanPACKAGE
- https://github.com/ckan/ckan/security/advisories/GHSA-mcvf-jxcw-vj73WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-41255ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan