Advisories
Flaws in things people run, newest first. The level comes from evidence, never from how alarming it sounds.
- For your digestdjango: Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
Fix: django 6.1.1 / 6.0.8 / 5.2.17
CVE-2026-15830 ·
- For your digestdjango: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
Fix: django 6.0.8 / 5.2.17
CVE-2026-15307 ·
- For your digestdjango: Django: DomainNameValidator permits newline characters that may enable HTTP header injection
Fix: django 6.0.7 / 5.2.16
CVE-2026-53878 ·
Fix: django 6.0.7 / 5.2.16
CVE-2026-53877 ·
- For your digestdjango: Django: cache middleware may expose private responses when unrelated request cookies are present
Fix: django 6.0.7 / 5.2.16
CVE-2026-48588 ·
- For your digestdjango: Django: has_vary_header may expose cached responses when Vary values contain whitespace
Fix: django 6.0.6 / 5.2.15
CVE-2026-48587 ·
- For your digestdjango: Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary
Fix: django 6.0.6 / 5.2.15
CVE-2026-35193 ·
- For your digestdjango: Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling
Fix: django 6.0.6 / 5.2.15
CVE-2026-8404 ·
- For your digestdjango: Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake
Fix: django 6.0.6 / 5.2.15
CVE-2026-7666 ·
Fix: django 6.0.6 / 5.2.15
CVE-2026-6873 ·
Fix: django 6.0.5 / 5.2.14
CVE-2026-35192 ·
- For your digestdjango: Django Uses Cache Containing Sensitive Information
Fix: django 6.0.5 / 5.2.14
CVE-2026-6907 ·
Fix: django 6.0.5 / 5.2.14
CVE-2026-5766 ·
- For your digestdjango: Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
Fix: django 6.0.4 / 5.2.13 / 4.2.30
CVE-2026-33034 ·
- For your digestdjango: Django has potential DoS via MultiPartParser through crafted multipart uploads
Fix: django 6.0.4 / 5.2.13 / 4.2.30
CVE-2026-33033 ·
Fix: django 6.0.4 / 5.2.13 / 4.2.30
CVE-2026-4292 ·
Fix: django 6.0.4 / 5.2.13 / 4.2.30
CVE-2026-4277 ·
Fix: django 6.0.4 / 5.2.13 / 4.2.30
CVE-2026-3902 ·
- For your digestdjango: Django has a Race Condition vulnerability
Fix: django 6.0.3 / 5.2.12 / 4.2.29
CVE-2026-25674 ·
Fix: django 6.0.3 / 5.2.12 / 4.2.29
CVE-2026-25673 ·
- For your digestdjango: Django has Inefficient Algorithmic Complexity
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2025-14550 ·
- For your digestdjango: Django has an SQL Injection issue
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2026-1312 ·
- For your digestdjango: Django has an SQL Injection issue
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2026-1287 ·
- For your digestdjango: Django has Inefficient Algorithmic Complexity
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2026-1285 ·
- For your digestdjango: Django has an SQL Injection issue
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2026-1207 ·
- For your digestdjango: Django has Observable Timing Discrepancy
Fix: django 6.0.2 / 5.2.11 / 4.2.28
CVE-2025-13473 ·
Fix: django 5.2.9 / 5.1.15 / 4.2.27
CVE-2025-64460 ·
Fix: django 5.2.9 / 5.1.15 / 4.2.27
CVE-2025-13372 ·
- For your digestdjango: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.
Fix: django 5.2.8 / 5.1.14 / 4.2.26
CVE-2025-64459 ·
- For your digestdjango: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
Fix: django 5.2.8 / 5.1.14 / 4.2.26
CVE-2025-64458 ·
Fix: django 5.2.7 / 5.1.13 / 4.2.25
CVE-2025-59682 ·
- For your digestdjango: Django vulnerable to SQL injection in column aliases
Fix: django 5.2.7 / 5.1.13 / 4.2.25
CVE-2025-59681 ·
Fix: django 5.2.2 / 5.1.10 / 4.2.22
CVE-2025-48432 ·
Fix: django 5.2.1 / 5.1.9 / 4.2.21
CVE-2025-32873 ·
- For your digestdjango: Django Potential Denial of Service (DoS) on Windows
Fix: django 5.1.8 / 5.0.14
CVE-2025-27556 ·
Fix: django 5.1.7 / 5.0.13 / 4.2.20
CVE-2025-26699 ·
Fix: django 5.1.5 / 5.0.11 / 4.2.18
CVE-2024-56374 ·
- For your digestdjango: Django SQL injection in HasKey(lhs, rhs) on Oracle
Fix: django 5.1.4 / 5.0.10 / 4.2.17
CVE-2024-53908 ·
Fix: django 5.1.4 / 5.0.10 / 4.2.17
CVE-2024-53907 ·
- For your digestdjango: Django allows enumeration of user e-mail addresses
Fix: django 5.1.1 / 5.0.9 / 4.2.16
CVE-2024-45231 ·
- For your digestdjango: Django vulnerable to denial-of-service attack via the urlize() and urlizetrunc() template filters
Fix: django 5.1.1 / 5.0.9 / 4.2.16
CVE-2024-45230 ·
- For your digestdjango: Django SQL injection vulnerability
Fix: django 5.0.8 / 4.2.15
CVE-2024-42005 ·
- For your digestdjango: Django vulnerable to denial-of-service attack
Fix: django 5.0.8 / 4.2.15
CVE-2024-41991 ·
- For your digestdjango: Django vulnerable to a denial-of-service attack
Fix: django 5.0.8 / 4.2.15
CVE-2024-41990 ·
- For your digestdjango: Django memory consumption vulnerability
Fix: django 5.0.8 / 4.2.15
CVE-2024-41989 ·
- For your digestdjango: Django vulnerable to Denial of Service
Fix: django 5.0.7 / 4.2.14
CVE-2024-39614 ·
- For your digestdjango: Django Path Traversal vulnerability
Fix: django 5.0.7 / 4.2.14
CVE-2024-39330 ·
- For your digestdjango: Django vulnerable to user enumeration attack
Fix: django 5.0.7 / 4.2.14
CVE-2024-39329 ·
- For your digestdjango: Django vulnerable to Denial of Service
Fix: django 5.0.7 / 4.2.14
CVE-2024-38875 ·
- For your digestdjango: Regular expression denial-of-service in Django
Fix: django 5.0.3 / 4.2.11 / 3.2.25
CVE-2024-27351 ·
Follow without an account:everything followedact nowthis weekJSONthis product