[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fosOVrHDM-MNxwvcODzWl2nGVJm5xYVJSwLUhlSTB9zQ":3},{"product":4,"cycleMajor":14,"releases":15,"cves":77,"nextMajor":124,"indexable":23},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"9605ebc6-f303-4cad-8660-9498c8793e02","django","Django","framework",null,"Developers leveraging Python for web development often rely on a robust framework to streamline their workflow, and Django has been a stalwart option since its inception. Created to facilitate rapid development and clean design, Django's model–template–views architectural pattern has made it a favorite among developers. With the Django Software Foundation at the helm, maintaining and supporting this framework, developers can trust that they have a reliable foundation for their projects. The fact that Django has been around for a while, with a substantial number of versions released over the years, is a testament to its enduring popularity and the active community that contributes to its growth.\n\nThe landscape of Django's versions reveals a story of continuous evolution, with a total of 22 versions released to date. Of these, 20 have reached their end-of-life, indicating that they no longer receive security updates or support. Currently, only 2 versions remain active, with the latest stable version being 6.0.6. Looking ahead, version 6.0 is slated to reach its end-of-life on 2027-04-30, marking an important milestone for developers who are still using this version. This transition underscores the importance of staying up-to-date with the latest versions to ensure the security and integrity of their applications. The most recent end-of-life transition occurred on 2026-04-07, when version 4.2 ceased to be supported.\n\nFrom a security standpoint, Django has been tracked for 55 known vulnerabilities, with 3 of these being critical. Version 5.2 is notably the most affected, with 21 vulnerabilities attributed to it. This highlights the need for developers to be vigilant about the versions they use and to prioritize updates to mitigate potential risks. Given the Known Exploited Vulnerabilities status that may apply to certain versions, it is crucial for developers to take proactive action to protect their applications. By migrating to the latest stable version, such as 6.0.6, developers can ensure they have the latest security patches and features, thereby safeguarding their projects against known and emerging threats.","https:\u002F\u002Fcdn.simpleicons.org\u002Fdjango","2026-10-07T02:00:12.028+00:00","2026-05-30T16:23:55.845073+00:00","1",[16,26,33,38,45,51,58,64,71],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":20,"eol_boolean":9,"latest":21,"latest_release_date":22,"lts":23,"support":24,"created_at":25},"c130a17a-b55c-46b6-a80c-d449451088b4","1.11","2017-04-04","2020-04-01","1.11.29","2020-03-04",true,"2017-12-02","2026-05-30T16:26:02.080235+00:00",{"id":27,"product_id":5,"cycle":28,"release_date":29,"eol":24,"eol_boolean":9,"latest":30,"latest_release_date":31,"lts":32,"support":19,"created_at":25},"7f9995bd-a3f6-43fd-b779-1eedae80424f","1.10","2016-08-01","1.10.8","2017-09-05",false,{"id":34,"product_id":5,"cycle":35,"release_date":36,"eol":19,"eol_boolean":9,"latest":37,"latest_release_date":19,"lts":32,"support":29,"created_at":25},"94922700-2f90-4907-91ac-e72794fd159f","1.9","2015-12-01","1.9.13",{"id":39,"product_id":5,"cycle":40,"release_date":41,"eol":42,"eol_boolean":9,"latest":43,"latest_release_date":44,"lts":32,"support":36,"created_at":25},"822af0ba-00c0-4c3d-9b72-c29700cffe24","1.8","2015-04-01","2018-04-01","1.8.19","2018-03-06",{"id":46,"product_id":5,"cycle":47,"release_date":48,"eol":36,"eol_boolean":9,"latest":49,"latest_release_date":50,"lts":32,"support":41,"created_at":25},"c4332f56-e965-4826-bf33-af85afda681e","1.7","2014-09-03","1.7.11","2015-11-24",{"id":52,"product_id":5,"cycle":53,"release_date":54,"eol":41,"eol_boolean":9,"latest":55,"latest_release_date":56,"lts":32,"support":57,"created_at":25},"8163ad25-bd70-49e7-8c57-8a34de4b850a","1.6","2013-11-06","1.6.11","2015-03-18","2014-09-02",{"id":59,"product_id":5,"cycle":60,"release_date":61,"eol":57,"eol_boolean":9,"latest":62,"latest_release_date":63,"lts":32,"support":54,"created_at":25},"6232bcd0-c56b-47f4-a145-b3008b191e8a","1.5","2013-02-26","1.5.12","2015-01-02",{"id":65,"product_id":5,"cycle":66,"release_date":67,"eol":68,"eol_boolean":9,"latest":69,"latest_release_date":70,"lts":32,"support":61,"created_at":25},"afdfd554-75dc-467c-9714-dfcdd8b1bcc3","1.4","2012-03-23","2015-10-01","1.4.22","2015-08-18",{"id":72,"product_id":5,"cycle":73,"release_date":74,"eol":61,"eol_boolean":9,"latest":75,"latest_release_date":76,"lts":32,"support":67,"created_at":25},"10d87741-f620-46d2-bf16-f1ec27bbbde8","1.3","2011-03-23","1.3.7","2013-02-21",[78,86,87,88,89,90,91,92,93,94,100,101,102,103,104,105,106,107,108,116,117,118,119,120,121,122,123],{"cveId":79,"releaseId":52,"cycle":53,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},"CVE-2026-15830","An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.\nGeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected.\nEa","MEDIUM",5.3,0.00763,"2026-08-04T17:16:46.593+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-15830",{"cveId":79,"releaseId":46,"cycle":47,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":34,"cycle":35,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":39,"cycle":40,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":72,"cycle":73,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":17,"cycle":18,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":27,"cycle":28,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":59,"cycle":60,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":79,"releaseId":65,"cycle":66,"description":80,"severity":81,"cvssScore":82,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},{"cveId":95,"releaseId":39,"cycle":40,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},"CVE-2026-15337","An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.\n`django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_M",0.0059,"2026-08-04T17:16:46.453+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-15337",{"cveId":95,"releaseId":72,"cycle":73,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":59,"cycle":60,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":27,"cycle":28,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":52,"cycle":53,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":34,"cycle":35,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":65,"cycle":66,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":17,"cycle":18,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":95,"releaseId":46,"cycle":47,"description":96,"severity":81,"cvssScore":82,"epssScore":97,"inKev":32,"publishedAt":98,"url":99},{"cveId":109,"releaseId":27,"cycle":28,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},"CVE-2026-15307","An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.\nGeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict","HIGH",8.8,0.01094,"2026-08-04T17:16:46.127+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-15307",{"cveId":109,"releaseId":72,"cycle":73,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":65,"cycle":66,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":59,"cycle":60,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":46,"cycle":47,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":39,"cycle":40,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":52,"cycle":53,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":17,"cycle":18,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},{"cveId":109,"releaseId":34,"cycle":35,"description":110,"severity":111,"cvssScore":112,"epssScore":113,"inKev":32,"publishedAt":114,"url":115},"2"]