How severe is GHSA-mcvf-jxcw-vj73?

GHSA-mcvf-jxcw-vj73 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mcvf-jxcw-vj73?

GHSA-mcvf-jxcw-vj73 affects the following packages: ckan (PyPI), ckan (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-mcvf-jxcw-vj73?

Update ckan to 2.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcvf-jxcw-vj73 is resolved across your whole dependency graph.

How do I detect GHSA-mcvf-jxcw-vj73 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mcvf-jxcw-vj73 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mcvf-jxcw-vj73?

O3 pinpoints whether GHSA-mcvf-jxcw-vj73 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mcvf-jxcw-vj73 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mcvf-jxcw-vj73 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mcvf-jxcw-vj73 published, and has it been updated?

GHSA-mcvf-jxcw-vj73 was published on April 29, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-mcvf-jxcw-vj73

MEDIUM

GHSA-mcvf-jxcw-vj73 is a medium-severity (CVSS 6.1) vulnerability in ckan. O3 Security confirms whether GHSA-mcvf-jxcw-vj73 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

CKAN has CSRF exemption primed by anonymous requests

Also known asCVE-2026-41255PYSEC-2026-2418

Published

Apr 29, 2026

Updated

Jul 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐍ckan🐍ckan

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Views can be marked as exempt from CSRF protection

Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection.

The marking was a member variable in flask-wtf.csrf.CSRFProtect(), which was stored as a module level variable in the flask_app middleware. Thsi API was never intended for request level changes, it is primarily a decorator for static configuration.

An unauthenticated request could hit a protected endpoint, exempting it from CSRF protection for the life of the particular server process. (e.g. one worker of uwsgi).

This could be leveraged with XSS to perform actions using other user's credentials.

References

Vulnerability report by @Shirshaw64p (original reporter)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ckan`	≥ 2.10.0&&< 2.10.10	2.10.10
🐍PyPI	`ckan`	≥ 2.11.0&&< 2.11.5	2.11.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ckan to 2.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcvf-jxcw-vj73 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mcvf-jxcw-vj73 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mcvf-jxcw-vj73. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Views can be marked as exempt from CSRF protection Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection. The marking was a member variable in flask-wtf.csrf.CSRFProtect(), which was stored as a module level variable in the flask_app middleware. Thsi API was never intended for request level changes, it is primarily a decorator for static configuration. An unauthenticated request could hit a protected endpoint, exempting it from CSRF protection for the life of the particular server process. (e.g. one worker of uwsgi). This could b

O3 Security · Impact-Aware SCA

Is GHSA-mcvf-jxcw-vj73 in your dependencies?

O3 detects GHSA-mcvf-jxcw-vj73 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works