https://seclists.org/oss-sec/2026/q2/35: Django CVE-2026-3902, CVE-2026-4277, CVE-2026-4292, CVE-2026-33033, and CVE-2026-33034
Published Apr 7, 2026
·Updated
Affected Software
4 affected components
Django Django (main)
Django Django 6.0<6.0.4
Django Django 5.2<5.2.13
Django Django 4.2<4.2.30
Frequently Asked Questions
1
What is the severity of CVE-2026-3902?
CVE-2026-3902 is classified as a high-severity vulnerability affecting Django.
2
How do I fix CVE-2026-4277?
To fix CVE-2026-4277, upgrade to the latest Django release that addresses this vulnerability.
3
What versions of Django are affected by CVE-2026-4292?
CVE-2026-4292 affects Django versions 6.0, 5.2, and 4.2.
4
What specific issues are introduced by CVE-2026-33033?
CVE-2026-33033 introduces security weaknesses that may allow unauthorized access to sensitive data.
5
What should I do after applying the patch for CVE-2026-33034?
After applying the patch for CVE-2026-33034, verify that your application functions correctly and monitor for unusual activity.