Authorization Flaw in ckan (CVE-2026-42031)
Summary
Vulnerability in ckan (CVE-2026-42031). Successful exploitation can lead to full system takeover. Exploitable via datastore_search_sql. Mitigation: upgrade to 2.11.5 or later.
Original description
The description as published by the source.
Impact
A vulnerability in datastore_search_sql allowed attackers to inject SQL in order to gain access to private resources and PostgreSQL system information.
Patches
The issue has been patched in CKAN 2.10.10 and CKAN 2.11.5
Workarounds
Disable the DataStore SQL search (ckan.datastore.sqlsearch.enabled = false). Note that the SQL search is disabled by default.
More information
As stated in the documentation, this action function has protections that offer some safety but are not designed to prevent all types of abuse. Depending on the sensitivity of private data in a project's DataStore and the likelihood of abuse of a consuming site, a developer may choose to disable this action function or restrict its use with a IAuthFunctions plugin.
Credits
- Reported by Arvin Shivram of Brutecat Security
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42031 has been found in ckan.
Attackers can target a specific entry point like datastore_search_sql over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade ckan to 2.11.5 or later.
If unsure, ask your IT team or search "ckan CVE-2026-42031" on the vendor's site.
CVE-2026-42031 (ckan) — CWE-863 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: datastore_search_sql / IAuthFunctions
Patched: 2.11.5 — apply immediately
Workaround: Disable the DataStore SQL search (ckan.datastore.sqlsearch.enabled = false).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in ckan. Attackers reach the vulnerable code path via datastore_search_sql without authentication.
Check the vendor advisory for the affected versions of ckan. Attack surface: datastore_search_sql / IAuthFunctions.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.11.5.
Workaround: Disable the DataStore SQL search (ckan.datastore.sqlsearch.enabled = false).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ckan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ckan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ckanを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable the DataStore SQL search (`ckan.datastore.sqlsearch.enabled = false`).パッチが適用されるまでの応急処置として、Disable the DataStore SQL search (
ckan.datastore.sqlsearch.enabled = false). を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade ckan to 2.11.5ステージング環境で 2.11.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web docs.ckan.org
- web docs.ckan.org
- web docs.ckan.org
- web docs.ckan.org
- web github.com