dbcve.org
CkanApplication · Okfn

CVE-2026-42031

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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, a vulnerability in datastore_search_sql allowed attackers to inject SQL in order to gain access to private resources and PostgreSQL system information 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

SQL injection vulnerability in CKAN's datastore_search_sql endpoint allows unauthenticated attackers to inject arbitrary SQL queries. This enables access to private data resources and extraction of PostgreSQL system information including database schema, user credentials, and configuration details. The vulnerability affects versions prior to 2.10.10 and 2.11.5.

MitigationUpgrade CKAN to version 2.10.10 or 2.11.5 or later. If immediate upgrade is not possible, restrict or disable the datastore_search_sql endpoint at the web server or application layer until the patch can be applied.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 CKAN version via API
    Send a GET request to /api/3/action/status_show or /api/version and look for the 'version' field in the JSON response
    Affected if The reported version is less than 2.10.10, or greater than or equal to 2.11.0 but less than 2.11.5
  2. Verify datastore extension is enabled
    Check CKAN configuration (usually in production.ini or development.ini) for the 'ckan.plugins' setting and confirm 'datastore' is listed among enabled plugins
    Affected if The datastore extension is enabled and the version is vulnerable as per step 1
  3. Confirm datastore_search_sql endpoint is accessible
    Attempt a GET request to /api/3/action/datastore_search_sql - if the endpoint responds (even with a parameter error), it is reachable
    Affected if The endpoint returns a response, indicating it is exposed and callable by unauthenticated users
  4. Check if endpoint accepts SQL parameters
    Send a request to /api/3/action/datastore_search_sql with a test SQL parameter (e.g., ?sql=SELECT+1) and observe if it processes the query
    Affected if The endpoint accepts and processes SQL input without sanitization, confirming the injection point exists

If CKAN version is below 2.10.10 or between 2.11.0 and 2.11.5, the datastore extension is enabled, and the datastore_search_sql endpoint is accessible and processes raw SQL, the environment is affected by this vulnerability.

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 or later. If immediate upgrade is not possible, restrict or disable the datastore_search_sql endpoint at the web server or application layer until the patch can be applied.

Recommended fix High confidence

Upgrade to CKAN 2.10.10 or CKAN 2.11.5 (whichever is compatible with your deployment)

  1. Backup your current CKAN installation and database before proceeding
  2. Identify your current CKAN version (typically in /etc/ckan/default/production.ini or via ckan --version)
  3. If running CKAN 2.10.x: Upgrade to version 2.10.10 or later
  4. If running CKAN 2.11.0-2.11.4: Upgrade to version 2.11.5 or later
  5. Follow standard CKAN upgrade procedures for your deployment method (pip install, package manager, or source)
  6. Restart CKAN services (paster serve, gunicorn, or your web server)
  7. Verify the upgrade was successful by checking the CKAN version
  8. Test that the datastore_search_sql endpoint is functioning correctly with intended queries
Caveat Security patch releases typically contain minimal breaking changes; review CKAN release notes for any deprecation notices

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

Fix this in Ckan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42031 — 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-42031 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