CVE-2026-41255: ckan · Cross-Site Request Forgery
Affects ckanSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 2.11.5 or 2.10.10 when convenient.
Data as of 11 Nov 2026, 23:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.1 |
|---|
- Patch
- Available – fixed in 2.11.5, 2.10.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade ckan to 2.11.5 or 2.10.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ckan ckan | Affected
| Fixed in
|
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.