CVE-2026-41255
PyPI vulnerability
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.
Affected products
PyPI. The exact versions are in the references.
What to do now
- Check your exposureFind out whether PyPI runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/ckan/ckan/security/advisories/GHSA-mcvf-jxcw-vj73
- docs.ckan.org/en/2.10/changelog.html#v-2-10-10-2026-04-29
- docs.ckan.org/en/2.11/changelog.html#v-2-11-5-2026-04-29
- github.com/advisories/GHSA-mcvf-jxcw-vj73
- github.com/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255
- nvd.nist.gov/vuln/detail/CVE-2026-41255
- nvd.nist.gov/vuln/detail/CVE-2026-41255
- cve.org/CVERecord?id=CVE-2026-41255
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.