# CKAN has no certificate validation on STMP connection

Advisory record · `GHSA-mpfm-fpgx-647q`

- **Identifiers:** `GHSA-mpfm-fpgx-647q` · `CVE-2026-41132` · `PYSEC-2026-2419`
- **State:** Confirmed
- **Severity:** CVSS 6.6 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 29 Apr 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Apr 2026, 20:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ckan` (PyPI): affected `>=2.11.0, <2.11.5 || <2.10.10`; fixed in `2.11.5`, `2.10.10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> CKAN versions before 2.10.10 and from 2.11.0 before 2.11.5 do not validate certificates on SMTP connections. An attacker in a position to intercept network traffic between CKAN and its configured mail server could impersonate that server using any certificate, such as a self-signed one, and capture SMTP credentials and email content. Upgrade to CKAN 2.10.10 or 2.11.5. The source gives no workaround.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.6 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 9th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 13 May 2026, 19:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-41132)
- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mpfm-fpgx-647q)

## Sources

- [GitHub Advisory Database: GHSA-mpfm-fpgx-647q](https://github.com/advisories/GHSA-mpfm-fpgx-647q)
- [OSV: GHSA-mpfm-fpgx-647q](https://osv.dev/vulnerability/GHSA-mpfm-fpgx-647q)
- <https://github.com/ckan/ckan/security/advisories/GHSA-mpfm-fpgx-647q>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41132>
- <https://docs.ckan.org/en/2.10/changelog.html#v-2-10-10-2026-04-29>
- <https://docs.ckan.org/en/2.11/changelog.html#v-2-11-5-2026-04-29>
- <https://github.com/ckan/ckan>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mpfm-fpgx-647q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mpfm-fpgx-647q/>. Everything for agents: <https://agentprime.io/llms.txt>.