Quick answers
- Is CVE-2026-42031 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42031 being exploited in the wild.
- How severe is CVE-2026-42031?
- High severity, with a CVSS score of 4, published 13 May 2026.
- Which products and versions are affected?
- CKAN < 2.10.10, < 2.11.5, < 2.10.10, >= 2.11.0, <= 2.11.4; ckan (PyPI) ECOSYSTEM:introduced=0,fixed=2.10.10, ECOSYSTEM:introduced=0,fixed=2.10.10,introduced=2.11.0,fixed=2.11.5.
- Is there a fix for CVE-2026-42031?
- Yes. ckan (PyPI): upgrade to 2.10.10, 2.11.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42031 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42031?
- Check whether you run CKAN or ckan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ckan (PyPI): upgrade to 2.10.10, 2.11.5 or later
pip install "ckan>=2.11.5"
Technical details
A vulnerability exists in the `datastore_search_sql` action function of CKAN due to improper neutralization of special elements in SQL commands (CWE-89) and incorrect authorization (CWE-863). An unauthenticated remote attacker can execute arbitrary SQL queries via the DataStore API to bypass access controls and retrieve private resources or PostgreSQL system metadata. The vulnerability is present when the `ckan.datastore.sqlsearch.enabled` configuration is set to true (it is disabled by default). The issue has been addressed in versions 2.10.10 and 2.11.5. As a workaround, administrators can disable the DataStore SQL search feature.
Affected products
- CKAN ckan < 2.10.10, >= 2.11.0, <= 2.11.4
Identifiers
- CVE-2026-42031
- GHSA-h7j7-3rx6-xvcg
- PYSEC-2026-2417
Timeline
- 2026-04-29: disclosed
- 2026-04-29: patched
- 2026-04-29: advisory