django CMS 3.11 & 4.1 Reach End of Life: Final Patch Releases and What to Do Next
April 2026 officially closed the chapter on two long-standing django CMS LTS branches: 3.11 and 4.1.
Their final patch releases wrap up maintenance with a focused set of bug fixes and security updates—no new features, just stability and safety as these versions reach end of life.
What landed in the final patches
Both branches received the usual “last mile” treatment: fixes that had been backported from newer versions, small regressions addressed, and compatibility tweaks for supported Django/Python versions.
On the 3.11 side, the last releases concentrated on admin behavior, UI inconsistencies, and long-standing edge cases in page handling. The most notable fix was a security issue involving improper escaping of page titles, which could allow JavaScript injection under certain conditions (thanks to Sanjok Karki, Javi Escribano, and galbadrakhtergel0820 for responsibly reporting the issue).
For 4.1, the final patches fixed content and data handling issues (ensured proper queryset iteration and corrected empty rendering for fallback languages), improved developer and admin behavior (added a page_title parameter to create_page and resolved unintended side effects in GrouperAdmin readonly fields), and patched the same security issue.
Across both branches, contributors submitted fixes via pull requests that were carefully reviewed and backported—ensuring users end on the most stable versions possible.
End of life means no safety net
With LTS support ending in April 2026, neither 3.11 nor 4.1 will receive:
- Security patches
- Bug fixes
- Compatibility updates
Running them in production going forward means accepting growing risk—especially as the Django ecosystem continues to move on.
Recommended upgrade path
If you’re still on 3.11, don’t jump straight to the latest release. The safer path is incremental: 3.11 → 4.1 → 5.0 (current LTS). django CMS 4.1 introduces architectural changes that are easier to adopt step-by-step
If you’re already on 4.1, your next move is simpler: 4.1 → 5.0
Version 5.0 is the current LTS and where active development, fixes, and ecosystem support are focused.
A quiet but important milestone
Final patch releases rarely get much attention, but they represent years of accumulated fixes and community effort distilled into a stable endpoint. They also mark a clear boundary: from here on, stability depends on upgrading, not waiting.
If you haven’t moved yet, now is the time—while your system is still predictable and before small issues turn into blockers.
Additional resources:
Fabian Braun
django CMS Fellow
Release
django CMS 5.1 is here: easier setup, flexible deployments, and a fresh editing experience
This release reduces friction across the whole project lifecycle: creating a new project, adding django CMS to an existing Django application, configuring larger deployments, controlling which plugins editors can use, and working with the CMS every day.
Release
django CMS 5.0.9 released: security, accessibility, and stability improvements
This release addresses three medium-severity security vulnerabilities and includes improvements to accessibility, Django compatibility, permissions, Content Security Policy support, and general editor stability.
Case Studies
How we built our professional services digital platform using django CMS
Compound Partners is a UK digital consultancy specialising in audience-centric user experience and content architecture for professional services firms. Fifteen years ago, a developer's recommendation pointed us at django CMS. Today, our entire business is built on it.