Is django 1.10 vulnerable?

PyPI · 9 releases from 1.10.0 to 1.10.8 · latest django is 6.1.3 · checked 18 Nov 2026

Yes: 17 known advisories

Yes. django 1.10.8, the last 1.10 release, is affected by 17 known security advisories (3 critical, 4 high, 6 medium, 4 low), including CVE-2025-64459, CVE-2020-7471, CVE-2019-19844. 5 more affect earlier 1.10.x releases. Upgrade to 5.2.17 or later to fix all of them.

Upgrade with:pip install 'django>=5.2.17'

Is your project on an affected django?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting django 1.10.8

  • HighCVE-2026-15307GHSA-wvqv-fj8w-qmhm4 Aug 2026

    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
  • MediumCVE-2026-15830GHSA-q238-5cxm-5c9h4 Aug 2026

    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
  • MediumCVE-2026-53878GHSA-8qcx-xf44-272x7 Jul 2026

    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
  • MediumCVE-2026-53877GHSA-crhf-3pfg-w68w7 Jul 2026

    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
  • LowCVE-2026-48588GHSA-3h9f-r86x-qvjx7 Jul 2026

    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
  • LowCVE-2026-8404GHSA-8cjm-8mp7-r2xf3 Jun 2026

    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
  • LowCVE-2026-48587GHSA-923m-gv2p-w5qp3 Jun 2026

    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
  • LowCVE-2026-6873GHSA-h7pc-vwp9-298g3 Jun 2026

    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
  • CriticalCVE-2025-64459GHSA-frmv-pr5f-9mcr5 Nov 2025

    Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.

    Affected
    >=5.2a1 <5.2.8 · >=5.0a1 <5.1.14 · <4.2.26
    Fixed in
    4.2.26, 5.1.14, 5.2.8
  • HighCVE-2025-64458GHSA-qw25-v68c-qjf35 Nov 2025

    Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows

    Affected
    >=5.2a1 <5.2.8 · >=5.0a1 <5.1.14 · <4.2.26
    Fixed in
    4.2.26, 5.1.14, 5.2.8
  • HighCVE-2025-57833GHSA-6w2r-r2m5-xq5w8 Sept 2025

    Django is subject to SQL injection through its column aliases

    Affected
    <4.2.24 · >=5.0a1 <5.1.12 · >=5.2a1 <5.2.6
    Fixed in
    4.2.24, 5.1.12, 5.2.6
  • MediumCVE-2025-48432GHSA-7xr5-9hcq-chf95 Jun 2025

    Django Improper Output Neutralization for Logs vulnerability

    Affected
    >=5.2 <5.2.2 · >=5.0a1 <5.1.10 · <4.2.22
    Fixed in
    4.2.22, 5.1.10, 5.2.2
  • MediumCVE-2024-45231GHSA-rrqc-c2jx-6jgv8 Oct 2024

    Django allows enumeration of user e-mail addresses

    Affected
    >=5.1 <5.1.1 · >=5.0 <5.0.9 · <4.2.16
    Fixed in
    4.2.16, 5.0.9, 5.1.1
  • HighCVE-2022-36359GHSA-8x94-hmjh-97hq11 Aug 2022

    Django vulnerable to Reflected File Download attack

    Affected
    <3.2.15 · >=4.0 <4.0.7
    Fixed in
    3.2.15, 4.0.7
  • MediumCVE-2021-33203GHSA-68w8-qjq3-2gfm10 Jun 2021

    Path Traversal in Django

    Affected
    <2.2.24 · >=3.0 <3.1.12 · >=3.2 <3.2.4
    Fixed in
    2.2.24, 3.1.12, 3.2.4
  • CriticalCVE-2020-7471GHSA-hmr4-m2h5-33qx11 Feb 2020

    SQL injection in Django

    Affected
    <1.11.28 · >=2.0 <2.2.10 · >=3.0 <3.0.3
    Fixed in
    1.11.28, 2.2.10, 3.0.3
  • CriticalCVE-2019-19844GHSA-vfq6-hq5r-27r616 Jan 2020

    Django Potential account hijack via password reset form

    Affected
    <1.11.27 · >=2.0 <2.2.9 · >=3.0 <3.0.1
    Fixed in
    1.11.27, 2.2.9, 3.0.1

Fixed within 1.10.x, affecting earlier releases

  • CriticalCVE-2016-9014GHSA-3f2c-jm6v-cr3517 May 2022

    Django DNS Rebinding Vulnerability

    Affected
    >=1.8a1 <1.8.16 · >=1.9a1 <1.9.11 · >=1.10a1 <1.10.3
    Fixed in
    1.8.16, 1.9.11, 1.10.3
  • CriticalCVE-2016-9013GHSA-mv8g-fhh6-626717 May 2022

    Django user with hardcoded password created when running tests on Oracle

    Affected
    >=1.10a1 <1.10.3 · >=1.9a1 <1.9.11 · >=1.8a1 <1.8.16
    Fixed in
    1.8.16, 1.9.11, 1.10.3
  • MediumCVE-2017-12794GHSA-9r8w-6x8c-6jr94 Jan 2019

    Django vulnerable to XSS on 500 pages

    Affected
    >=1.10a1 <1.10.8 · >=1.11a1 <1.11.5
    Fixed in
    1.10.8, 1.11.5
  • MediumCVE-2017-7233GHSA-37hp-765x-j95x4 Jan 2019

    Django open redirect and possible XSS attack via user-supplied numeric redirect URLs

    Affected
    >=1.10a1 <1.10.7 · >=1.9a1 <1.9.13 · >=1.8a1 <1.8.18
    Fixed in
    1.8.18, 1.9.13, 1.10.7
  • MediumCVE-2017-7234GHSA-h4hv-m4h4-mhwg4 Jan 2019

    Django open redirect

    Affected
    >=1.10 <1.10.7 · >=1.9 <1.9.13 · >=1.8 <1.8.18
    Fixed in
    1.8.18, 1.9.13, 1.10.7

Every django 1.10.x release

Affected: 1.10.0 to 1.10.8. Latest django: 6.1.3.

VersionKnown advisories
django 1.10.8CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844
django 1.10.7CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794
django 1.10.6CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.5CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.4CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.3CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.2CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2016-9014, CVE-2016-9013, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.1CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2016-9014, CVE-2016-9013, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234
django 1.10.0CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2016-9014, CVE-2016-9013, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2017-12794, CVE-2017-7233, CVE-2017-7234

Which of your client projects are still on django 1.10?

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.