dbcve.org
CkanApplication · Okfn

CVE-2026-41132

HIGH · 7.4 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 →
83/100
Remediation priority · High
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, the configured SMTP server may be spoofed with any certificate (e.g. self-signed), leaving credentials and all emails sent open to MITM attacks. 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 · high confidence

CKAN's SMTP implementation fails to properly validate SSL/TLS certificates, allowing attackers to spoof the SMTP server with arbitrary certificates (including self-signed ones). This enables man-in-the-middle attacks, exposing SMTP credentials and all email content transmitted through the server.

MitigationUpgrade CKAN to version 2.10.10 or 2.11.5 to receive the patch, or ensure proper SSL certificate validation is enforced for SMTP connections.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/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. Identify CKAN installation version
    Run 'ckan version' from the CKAN environment, or check the version file in the CKAN source directory
    Affected if The installed version is less than 2.10.10, OR greater than or equal to 2.11.0 but less than 2.11.5
  2. Verify SMTP is configured
    Inspect the CKAN configuration file (commonly production.ini or development.ini) for [smtp] section entries such as smtp.server, smtp.user, and smtp.mail_from
    Affected if SMTP settings are present and CKAN is configured to send email through an SMTP server
  3. Check SSL certificate validation setting
    Look for the smtp.ssl_verify_cert setting in the CKAN configuration file - examine whether it is set to false, or is absent which may default to no validation
    Affected if The ssl_verify_cert option is set to false or is missing, indicating certificate validation is disabled
  4. Identify SMTP connection type
    Review smtp.server value to determine if SMTP over SSL/TLS is in use (typically port 465 for SMTPS or 587 for STARTTLS)
    Affected if SMTP is configured to use SSL/TLS on ports 465 or 587 and the version is vulnerable per step 1

A user is affected if CKAN is running a vulnerable version (less than 2.10.10 or between 2.11.0 and 2.11.5) with SMTP configured and SSL certificate validation is disabled or not properly enforced.

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 to receive the patch, or ensure proper SSL certificate validation is enforced for SMTP connections.

Recommended fix High confidence

Upgrade to CKAN 2.10.10 or CKAN 2.11.5

  1. 1. Back up the CKAN database and all configuration files
  2. 2. Stop the CKAN service
  3. 3. Upgrade CKAN to version 2.10.10 (if on 2.x) or 2.11.5 (if on 2.11.x) using the standard upgrade process (package manager or source installation)
  4. 4. Run database migrations if required: `ckan db upgrade` or check the upgrade guide for your installation method
  5. 5. Verify the SMTP configuration in the CKAN config file (`.ini`) uses valid TLS/SSL certificates
  6. 6. Restart the CKAN service
  7. 7. Test email functionality to confirm SMTP is working correctly with proper certificate validation
Caveat Review CKAN release notes for any breaking changes between your current version and 2.10.10/2.11.5 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ckan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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