# CKAN has CSRF exemption primed by anonymous requests

Advisory record · `GHSA-mcvf-jxcw-vj73`

- **Identifiers:** `GHSA-mcvf-jxcw-vj73` · `CVE-2026-41255` · `PYSEC-2026-2418`
- **State:** Confirmed
- **Severity:** CVSS 6.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.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:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## Machine-written summary

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

> CKAN versions 2.10.0 to before 2.10.10, and 2.11.0 to before 2.11.5, are affected. An unauthenticated request to a protected endpoint can remove CSRF protection from that endpoint for the lifetime of the server process, which can then be combined with cross-site scripting to perform actions using other users' credentials. Upgrade to CKAN 2.10.10 or 2.11.5. The source gives few details on the exact attack conditions.

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.1 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 2nd 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-41255)
- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mcvf-jxcw-vj73)

## Sources

- [GitHub Advisory Database: GHSA-mcvf-jxcw-vj73](https://github.com/advisories/GHSA-mcvf-jxcw-vj73)
- [OSV: GHSA-mcvf-jxcw-vj73](https://osv.dev/vulnerability/GHSA-mcvf-jxcw-vj73)
- <https://github.com/ckan/ckan/security/advisories/GHSA-mcvf-jxcw-vj73>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41255>
- <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/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255>
- <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-mcvf-jxcw-vj73>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mcvf-jxcw-vj73/>. Everything for agents: <https://agentprime.io/llms.txt>.