# CVE-2026-42031: CKAN: Unauthenticated SQL Injection and Authorization Bypass in `datastore_search_sql`

> Unauthenticated attackers can inject SQL to access private resources and PostgreSQL system information in CKAN data portals.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-h7j7-3rx6-xvcg, PYSEC-2026-2417

## What is CVE-2026-42031?

CVE-2026-42031 is a high-severity SQL injection vulnerability in ckan, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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, 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-42031?

5 open source packages ship an affected version, including ckan. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ckan` | PyPI | All versions | 2.10.10, 2.11.5 |
| `ckan` | PyPI | All versions | 2.10.10 |
| `ckan` | PyPI | All versions | 2.10.10 |
| `ckan` | PyPI | From 2.11.0 | 2.11.5 |
| `ckan` | PyPI | From 2.11.0 | 2.11.5 |

Products: Okfn Ckan.

## How do I fix CVE-2026-42031?

Upgrade ckan to a fixed version for your release line: 2.10.10 or 2.11.5.

## Is CVE-2026-42031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42031 exists.

Public exploit code:

- CVE-2026-42031 SQL Injection Scanner for CKAN DataStore (github_poc): https://github.com/ddrvahandzo90-hue/CVE-2026-42031-SQL-Injection-Scanner
- CKAN DataStore SQL Search - SQL Injection (nuclei): http/cves/2026/CVE-2026-42031.yaml

## Other vulnerabilities in ckan

- [CVE-2023-32321](https://insights.sbomify.com/CVE-2023-32321/): CKAN remote code execution and private information access via crafted resource ids (critical 9.8)
- [CVE-2023-32696](https://insights.sbomify.com/CVE-2023-32696/): Excessive permissions for ckan user (high 8.8)
- [CVE-2022-43685](https://insights.sbomify.com/CVE-2022-43685/): CKAN contains Improper Authentication leading to account takeover (high 8.8)
- [CVE-2023-22746](https://insights.sbomify.com/CVE-2023-22746/): CKAN is vulnerable to session secret shared across instances using Docker images (high 8.6)
- [CVE-2024-41675](https://insights.sbomify.com/CVE-2024-41675/): CKAN has a Cross-site Scripting vector in the Datatables view plugin (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42031 and fix it if it is affected.

What it is: CVE-2026-42031 is a high-severity SQL injection vulnerability in ckan, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42031 exists.

Affected packages and fixed versions:
- ckan (PyPI): affected all versions; fixed in 2.10.10, 2.11.5
- ckan (PyPI): affected all versions; fixed in 2.10.10
- ckan (PyPI): affected all versions; fixed in 2.10.10
- ckan (PyPI): affected from 2.11.0; fixed in 2.11.5
- ckan (PyPI): affected from 2.11.0; fixed in 2.11.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42031/ (Markdown: https://insights.sbomify.com/CVE-2026-42031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42031
- OSV: https://osv.dev/vulnerability/CVE-2026-42031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42031/
Summaries are generated and may contain mistakes; the official description above is the record.