Is django 6.0 vulnerable?
PyPI · 11 releases from 6.0.0 to 6.0.10 · latest django is 6.1.3 · checked 18 Nov 2026
No known advisories in the last release
django 6.0.10, the last 6.0 release, has no known advisories. 26 advisories affect earlier 6.0.x releases, so update to 6.0.10.
pip install 'django>=6.0.10'Is your project on an affected django?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 6.0.x, affecting earlier releases
Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
- Affected
- <5.2.17 · >=6.0a1 <6.0.8
- Fixed in
- 5.2.17, 6.0.8
Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
- Affected
- <5.2.17 · >=6.0a1 <6.0.8 · >=6.1a1 <6.1.1
- Fixed in
- 5.2.17, 6.0.8, 6.1.1
Django: DomainNameValidator permits newline characters that may enable HTTP header injection
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: GDALRaster may over-read heap memory when constructed from bytes
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: cache middleware may expose private responses when unrelated request cookies are present
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: has_vary_header may expose cached responses when Vary values contain whitespace
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: signed cookies are vulnerable to salt namespace collisions
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake
- Affected
- >=5.2 <5.2.15 · >=6.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary
- Affected
- >=5.2.0 <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django has an Improper Handling of Length Parameter Inconsistency
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django Uses Cache Containing Sensitive Information
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django Uses Persistent Cookies Containing Sensitive Information
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django vulnerable to ASGI header spoofing via underscore/hyphen conflation
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to privilege abuse in ModelAdmin.list_editable
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to privilege abuse in GenericInlineModelAdmin
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django has potential DoS via MultiPartParser through crafted multipart uploads
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to Uncontrolled Resource Consumption
- Affected
- >=6.0 <6.0.3 · >=5.2 <5.2.12 · >=4.2 <4.2.29
- Fixed in
- 4.2.29, 5.2.12, 6.0.3
Django has a Race Condition vulnerability
- Affected
- >=6.0 <6.0.3 · >=5.2 <5.2.12 · >=4.2 <4.2.29
- Fixed in
- 4.2.29, 5.2.12, 6.0.3
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Observable Timing Discrepancy
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Inefficient Algorithmic Complexity
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Inefficient Algorithmic Complexity
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Every django 6.0.x release
Affected: 6.0.0 to 6.0.7. 6.0.8 and later are not affected. Latest django: 6.1.3.
| Version | Known advisories |
|---|---|
| django 6.0.10 | None |
| django 6.0.9 | None |
| django 6.0.8 | None |
| django 6.0.7 | CVE-2026-15307, CVE-2026-15830 |
| django 6.0.6 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588 |
| django 6.0.5 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193 |
| django 6.0.4 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193, CVE-2026-5766, CVE-2026-6907, CVE-2026-35192 |
| django 6.0.3 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193, CVE-2026-5766, CVE-2026-6907, CVE-2026-35192, CVE-2026-3902, CVE-2026-4292, CVE-2026-4277, CVE-2026-33034, CVE-2026-33033 |
| django 6.0.2 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193, CVE-2026-5766, CVE-2026-6907, CVE-2026-35192, CVE-2026-3902, CVE-2026-4292, CVE-2026-4277, CVE-2026-33034, CVE-2026-33033, CVE-2026-25673, CVE-2026-25674 |
| django 6.0.1 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193, CVE-2026-5766, CVE-2026-6907, CVE-2026-35192, CVE-2026-3902, CVE-2026-4292, CVE-2026-4277, CVE-2026-33034, CVE-2026-33033, CVE-2026-25673, CVE-2026-25674, CVE-2026-1287, CVE-2026-1312, CVE-2026-1207, CVE-2025-13473, CVE-2025-14550, CVE-2026-1285 |
| django 6.0.0 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2026-7666, CVE-2026-35193, CVE-2026-5766, CVE-2026-6907, CVE-2026-35192, CVE-2026-3902, CVE-2026-4292, CVE-2026-4277, CVE-2026-33034, CVE-2026-33033, CVE-2026-25673, CVE-2026-25674, CVE-2026-1287, CVE-2026-1312, CVE-2026-1207, CVE-2025-13473, CVE-2025-14550, CVE-2026-1285 |
Which of your client projects are still on django 6.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact django version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other django versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.