Vulnerability in ckan (CVE-2026-41132)
Summary
Vulnerability in ckan (CVE-2026-41132). Confidential information can be exposed externally. Mitigation: upgrade to 2.10.10 or later.
Original description
The description as published by the source.
Impact
Configured SMTP server may be spoofed with any certificate (e.g. self-signed), leaving credentials and all emails sent open to MITM attacks.
Patches
The vulnerability has been patched in CKAN 2.10.10 and CKAN 2.11.5
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-41132 has been found in ckan.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade ckan to 2.10.10 or later.
If unsure, ask your IT team or search "ckan CVE-2026-41132" on the vendor's site.
CVE-2026-41132 (ckan) — CWE-295 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.10.10 — apply immediately
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.
A vulnerability (CWE-295) exists in ckan.
Check the vendor advisory for the affected versions of ckan.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 2.10.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade ckan to 2.10.10ステージング環境で 2.10.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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 github.com