https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:01:09 +0000 https://cve.radiocsirt.org/vuln/cve-2026-41255 <p><strong>Affected:</strong> ckan</p> <p>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, 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. This 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 vulnerability is fixed in 2.10.10 and 2.11.5.</p> <p><strong>Affected:</strong> ckan</p> <p>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, 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. This 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 vulnerability is fixed in 2.10.10 and 2.11.5.</p> https://cve.radiocsirt.org/vuln/cve-2026-41255 https://cve.radiocsirt.org/vuln/ghsa-mcvf-jxcw-vj73 <p><strong>Affected:</strong> PyPI: ckan</p> <p>Views can be marked as exempt from CSRF protection</p> <p>Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection.</p> <p>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.</p> <p>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).</p> <p>This could be leveraged with XSS to perform actions using other user&#39;s credentials.</p> <p>### References</p> <p>* [Vulnerability report](https://github.com/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255) by @Shirshaw64p (original reporter)</p> <p><strong>Affected:</strong> PyPI: ckan</p> <p>Views can be marked as exempt from CSRF protection</p> <p>Access to the views via tokens or unauthenticated requests marked the endpoint as not requiring CSRF protection.</p> <p>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.</p> <p>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).</p> <p>This could be leveraged with XSS to perform actions using other user&#39;s credentials.</p> <p>### References</p> <p>* [Vulnerability report](https://github.com/Shirshaw64p/security-advisories/tree/main/CVE-2026-41255) by @Shirshaw64p (original reporter)</p> https://cve.radiocsirt.org/vuln/ghsa-mcvf-jxcw-vj73