dbcve.org
CkanApplication · Okfn

CVE-2026-42032

CRITICAL · 9.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 →
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 bypass authorization 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 · moderate confidence

The vulnerability exists in the datastore_search_sql endpoint of CKAN, allowing attackers to bypass authorization controls and execute arbitrary SQL queries. This enables unauthorized access to private datasets and extraction of sensitive PostgreSQL system information including database schema, version details, and potentially credentials.

MitigationUpgrade CKAN to version 2.10.10 or 2.11.5 (or later) to patch the authorization bypass in datastore_search_sql. Until then, disable or restrict access to the datastore_search_sql endpoint as a temporary measure.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 your CKAN installation directory. Compare the version number to the affected ranges: < 2.10.10 or >= 2.11.0 and < 2.11.5.
    Affected if The installed version falls within < 2.10.10 or >= 2.11.0, < 2.11.5.
  2. Verify datastore extension is enabled
    Check your CKAN configuration file (usually `production.ini` or `ckan.ini`) for the line `ckan.plugins = ... datastore ...`. Also run `ckan plugin list` if available.
    Affected if The datastore plugin is listed among enabled plugins.
  3. Confirm datastore_search_sql endpoint is accessible
    Send a GET or POST request to `http://<your-ckan-host>/api/3/action/datastore_search_sql?sql=SELECT 1`. Check if the endpoint responds (authentication may still be improperly enforced).
    Affected if The endpoint returns a response without proper authorization failure.
  4. Inspect endpoint authorization configuration
    Review your CKAN configuration file for any `datastore_search_sql` specific auth settings. Check `ckan.auth.` parameters related to datastore. Also review any reverse proxy or API gateway access controls.
    Affected if No explicit authorization controls are configured for datastore_search_sql, or default allow is in effect.
  5. Review application logs for suspicious SQL queries
    Examine CKAN logs (typically in `/var/log/ckan/` or as configured) for entries containing datastore_search_sql with unexpected or unauthorized SQL patterns, especially queries accessing system tables like pg_database, pg_user, or information_schema.
    Affected if Log entries show unauthorized SQL queries through datastore_search_sql to sensitive PostgreSQL system tables.

Your environment is affected if CKAN version is less than 2.10.10 or between 2.11.0 and 2.11.5 (exclusive), the datastore plugin is enabled, and the datastore_search_sql endpoint is accessible without proper authorization controls.

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) to patch the authorization bypass in datastore_search_sql. Until then, disable or restrict access to the datastore_search_sql endpoint as a temporary measure.

Recommended fix High confidence

CKAN 2.10.10 (for 2.10.x line) or CKAN 2.11.5 (for 2.11.x line)

  1. Identify your current CKAN version by checking the installed package or running `ckan --version`
  2. If running CKAN 2.10.x: Upgrade to version 2.10.10 or later
  3. If running CKAN 2.11.x: Upgrade to version 2.11.5 or later
  4. Backup your CKAN database and configuration files before upgrading
  5. Apply the upgrade using your deployment method (e.g., pip install, package manager, or docker image)
  6. Restart the CKAN application services after upgrade
  7. Verify the new version is running correctly
  8. Confirm the datastore_search_sql endpoint now properly enforces authorization checks

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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