[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flZjCOtSn2GLs8dgZ9bY8RxbkDGEfvz5FlePRK3BKADg":3},{"product":4,"cycleMajor":14,"releases":15,"cves":38,"nextMajor":92},{"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,"Django is a free and open-source, Python-based web framework that runs on a web server. It follows the model–template–views (MTV) architectural pattern.","https:\u002F\u002Fcdn.simpleicons.org\u002Fdjango","2026-06-09T20:02:18.511+00:00","2026-05-30T16:23:55.845073+00:00","5",[16,26,33],{"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},"c8c51431-22d8-4514-a156-be032ed34d80","5.2","2025-04-02","2028-04-30","5.2.15","2026-06-03",true,"2025-12-03","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},"2c0fe166-113f-4a3f-97b7-0b733e55d53d","5.1","2024-08-07","5.1.15","2025-12-02",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},"2bd9bf4a-9c98-4dc8-90f1-a5b2a1b4f772","5.0","2023-12-04","5.0.14",[39,47,54,61,69,75,80,86],{"cveId":40,"releaseId":17,"cycle":18,"description":41,"severity":42,"cvssScore":43,"epssScore":44,"inKev":32,"publishedAt":45,"url":46},"CVE-2026-35192","An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.\nResponse headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Cantina for reporting this issue.","MEDIUM",6.5,0.00045,"2026-05-05T16:16:12.383+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-35192",{"cveId":48,"releaseId":17,"cycle":18,"description":49,"severity":42,"cvssScore":50,"epssScore":51,"inKev":32,"publishedAt":52,"url":53},"CVE-2026-5766","An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.\nASGI requests with a missing or understated `Content-Length` header can bypass the `FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading large files into memory and causing service degradation.\r\n \r\nAs a reminder, Django expects a limit to be configured at the web server level rather than solely relying on `FILE_UPLOAD_MAX_MEMORY_SIZE`.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and ",5.3,0.00056,"2026-05-05T16:16:17.74+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-5766",{"cveId":55,"releaseId":17,"cycle":18,"description":56,"severity":42,"cvssScore":57,"epssScore":58,"inKev":32,"publishedAt":59,"url":60},"CVE-2026-6907","An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.\n`django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Ahmad Sadeddin for reporting this issue.",4.3,0.00036,"2026-05-05T16:16:18.227+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-6907",{"cveId":62,"releaseId":17,"cycle":18,"description":63,"severity":64,"cvssScore":65,"epssScore":66,"inKev":32,"publishedAt":67,"url":68},"CVE-2026-48587","An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.\n`django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to than","LOW",3.1,0.0004,"2026-06-03T14:16:44.983+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-48587",{"cveId":70,"releaseId":17,"cycle":18,"description":71,"severity":64,"cvssScore":65,"epssScore":72,"inKev":32,"publishedAt":73,"url":74},"CVE-2026-8404","An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.\n`django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank A",0.00041,"2026-06-03T14:16:47.65+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-8404",{"cveId":76,"releaseId":17,"cycle":18,"description":77,"severity":64,"cvssScore":65,"epssScore":66,"inKev":32,"publishedAt":78,"url":79},"CVE-2026-35193","An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.\n`django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to","2026-06-03T14:16:41.247+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-35193",{"cveId":81,"releaseId":17,"cycle":18,"description":82,"severity":64,"cvssScore":65,"epssScore":83,"inKev":32,"publishedAt":84,"url":85},"CVE-2026-7666","An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15.\n`django.core.mail.backends.smtp.EmailBackend` in Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake when `fail_silently=True`, which allows on-path network attackers to read email content via cleartext interception.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Kasper Dupont fo",0.00013,"2026-06-03T14:16:47.087+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-7666",{"cveId":87,"releaseId":17,"cycle":18,"description":88,"severity":64,"cvssScore":65,"epssScore":89,"inKev":32,"publishedAt":90,"url":91},"CVE-2026-6873","An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15.\n`django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affec",0.00009,"2026-06-03T14:16:46.483+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-6873","6"]