dbcve.org
CkanApplication · Okfn

CVE-2026-41255

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 2.10.10 / 2.11.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CSRF protection bypass in CKAN where flask-wtf.csrf.CSRFProtect() module-level variable gets modified at request-time when unauthenticated requests access certain endpoints. This permanently disables CSRF protection for that specific server worker process, allowing attackers to craft CSRF attacks against authenticated users.

MitigationUpgrade CKAN to version 2.10.10 or 2.11.5 to receive the security patch that prevents request-time modification of the CSRF protection configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CkanApplication
Affected:< 2.10.10>= 2.11.0, < 2.11.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed CKAN version
    Run `ckan --version` or check the version file in the CKAN installation directory
    Affected if Version is < 2.10.10 or >= 2.11.0 and < 2.11.5
  2. Verify CSRF protection configuration
    Inspect the CKAN configuration file (typically .ini) for flask-wtf CSRF settings and check if CSRFProtect is being used in the application code
    Affected if CSRF protection is enabled but the application uses the vulnerable flask-wtf.csrf.CSRFProtect pattern without additional safeguards
  3. Check for exposed unauthenticated endpoints
    Review the CKAN routing configuration for endpoints accessible without authentication that may trigger the vulnerable code path
    Affected if Unauthenticated endpoints exist that can trigger the request-time modification of the CSRF protection variable

The environment is affected if CKAN version is less than 2.10.10 or between 2.11.0 and 2.11.5 inclusive, and the application exposes unauthenticated endpoints that can trigger the flask-wtf.csrf.CSRFProtect modification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.10 / 2.11.5 or later
Fixed in 2.10.102.11.5
Interim mitigation

Upgrade CKAN to version 2.10.10 or 2.11.5 to receive the security patch that prevents request-time modification of the CSRF protection configuration.

Recommended fix High confidence

CKAN 2.10.10 or CKAN 2.11.5 (depending on your major version branch)

  1. 1. Backup your current CKAN database and configuration files before proceeding
  2. 2. Identify your current CKAN version using `ckan --version` or checking your installed package
  3. 3. For CKAN 2.10.x users: Upgrade to version 2.10.10 or later
  4. 4. For CKAN 2.11.x users: Upgrade to version 2.11.5 or later
  5. 5. Apply the upgrade using your deployment method (e.g., pip install --upgrade ckan, package manager, or source installation)
  6. 6. Restart all CKAN services and workers (including uwsgi processes) to ensure the CSRF protection fix takes effect
  7. 7. Verify the upgrade was successful by checking the CKAN version
  8. 8. Test that CSRF protection is functioning correctly on your deployment
Caveat Review CKAN release notes for your target version to check for any breaking changes between your current version and the upgrade target

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ckan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41255 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41255 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data