VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django: vulnerability history, versions and safety

django is a package in the PyPI ecosystem. Vulert records 348 vulnerabilities for it across 120 releases, from Oct 2007 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
348 vulnerabilities recorded C16 H66 M63 L17 U186
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
76 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django vulnerabilities

Vulert verdict on django 6.1.2 i

Updated on 23 Oct 2026

Careful: 6.1.2 has 10 known vulnerabilities, and 6 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.1.2 — affected i
  • Vulnerabilities on record 348 over 18 years · 76 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 6 i
  • Depended on by 11,973 packages i
  • Stars 91,473 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for django, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.2.18 06 Oct 2026 H1 U9 BSD-3-Clause No Details →
6.0.9 06 Oct 2026 H1 U9 BSD-3-Clause No Details →
6.1.2 06 Oct 2026 H1 U9 BSD-3-Clause No Details →
6.1.1 02 Sep 2026 H1 U9 BSD-3-Clause No Details →
6.1.0 05 Aug 2026 H1 U9 BSD-3-Clause No Details →
5.2.17 04 Aug 2026 H1 U9 BSD-3-Clause No Details →
6.0.8 04 Aug 2026 H1 U9 BSD-3-Clause No Details →
6.1.0rc1 22 Jul 2026 H1 U9 BSD-3-Clause No Details →
5.2.16 07 Jul 2026 H1 M1 U2 BSD-3-Clause Yes Details →
6.0.7 07 Jul 2026 U2 BSD-3-Clause Yes Details →
6.1.0b1 24 Jun 2026 H1 U9 BSD-3-Clause No Details →
5.2.15 03 Jun 2026 H1 M3 L1 U5 BSD-3-Clause Yes Details →
6.0.6 03 Jun 2026 U5 BSD-3-Clause Yes Details →
6.1.0a1 20 May 2026 H1 U9 BSD-3-Clause No Details →
5.2.14 05 May 2026 H1 M3 L6 U10 BSD-3-Clause Yes Details →
6.0.5 05 May 2026 U10 BSD-3-Clause Yes Details →
4.2.30 07 Apr 2026 H1 M3 L4 U11 BSD-3-Clause Yes Details →
5.2.13 07 Apr 2026 H1 M3 L6 U13 BSD-3-Clause Yes Details →
6.0.4 07 Apr 2026 M1 L2 U13 BSD-3-Clause Yes Details →
4.2.29 03 Mar 2026 H1 M3 L4 U16 BSD-3-Clause Yes Details →
5.2.12 03 Mar 2026 H1 M3 L6 U18 BSD-3-Clause Yes Details →
6.0.3 03 Mar 2026 H2 M2 L4 U18 BSD-3-Clause Yes Details →
4.2.28 03 Feb 2026 H1 M3 L4 U18 BSD-3-Clause Yes Details →
5.2.11 03 Feb 2026 H1 M3 L6 U20 BSD-3-Clause Yes Details →
6.0.2 03 Feb 2026 H3 M2 L5 U20 BSD-3-Clause Yes Details →
6.0.1 06 Jan 2026 H6 M2 L8 U26 BSD-3-Clause Yes Details →
5.2.10 06 Jan 2026 H1 M3 L6 U26 BSD-3-Clause Yes Details →
6.0.0 03 Dec 2025 H7 M2 L8 U9 BSD-3-Clause No Details →
4.2.27 02 Dec 2025 H1 M3 L4 U24 BSD-3-Clause Yes Details →
5.1.15 02 Dec 2025 H1 M3 L4 U11 BSD-3-Clause Yes Details →
5.2.9 02 Dec 2025 H1 M3 L6 U26 BSD-3-Clause Yes Details →
6.0.0rc1 19 Nov 2025 H7 M2 L8 U9 BSD-3-Clause No Details →
4.2.26 05 Nov 2025 H1 M3 L4 U26 BSD-3-Clause Yes Details →
5.1.14 05 Nov 2025 H1 M3 L4 U13 BSD-3-Clause Yes Details →
5.2.8 05 Nov 2025 H1 M5 L6 U28 BSD-3-Clause Yes Details →
6.0.0b1 22 Oct 2025 H7 M2 L8 U9 BSD-3-Clause No Details →
4.2.25 01 Oct 2025 H1 M3 L4 U28 BSD-3-Clause Yes Details →
5.1.13 01 Oct 2025 H1 M3 L4 U15 BSD-3-Clause Yes Details →
5.2.7 01 Oct 2025 C1 H2 M5 L6 U30 BSD-3-Clause Yes Details →
6.0.0a1 17 Sep 2025 H7 M2 L8 U9 BSD-3-Clause No Details →
4.2.24 03 Sep 2025 H2 M3 L5 U30 BSD-3-Clause Yes Details →
5.1.12 03 Sep 2025 H1 M3 L4 U17 BSD-3-Clause Yes Details →
5.2.6 03 Sep 2025 C1 H2 M5 L6 U32 BSD-3-Clause Yes Details →
5.2.5 06 Aug 2025 C1 H2 M5 L6 U33 BSD-3-Clause Yes Details →
5.2.4 02 Jul 2025 C1 H2 M5 L6 U33 BSD-3-Clause Yes Details →
5.2.3 10 Jun 2025 C1 H2 M5 L6 U33 BSD-3-Clause Yes Details →
5.1.11 10 Jun 2025 H1 M3 L4 U18 BSD-3-Clause Yes Details →
4.2.23 10 Jun 2025 H3 M3 L5 U31 BSD-3-Clause Yes Details →
4.2.22 04 Jun 2025 H3 M3 L5 U31 BSD-3-Clause Yes Details →
5.1.10 04 Jun 2025 H1 M3 L4 U18 BSD-3-Clause Yes Details →
5.2.2 04 Jun 2025 C1 H2 M5 L6 U33 BSD-3-Clause Yes Details →
4.2.21 07 May 2025 H3 M3 L5 U32 BSD-3-Clause Yes Details →
5.1.9 07 May 2025 H1 M3 L4 U19 BSD-3-Clause Yes Details →
5.2.1 07 May 2025 C1 H2 M6 L6 U43 BSD-3-Clause Yes Details →
5.2.0 02 Apr 2025 C1 H3 M6 L6 U32 BSD-3-Clause No Details →
5.0.14 02 Apr 2025 H1 M3 L4 U11 BSD-3-Clause Yes Details →
5.1.8 02 Apr 2025 H1 M3 L4 U20 BSD-3-Clause Yes Details →
5.2.0rc1 19 Mar 2025 C1 H3 M6 L5 U32 BSD-3-Clause No Details →
4.2.20 06 Mar 2025 H3 M4 L5 U33 BSD-3-Clause Yes Details →
5.0.13 06 Mar 2025 H1 M4 L4 U12 BSD-3-Clause Yes Details →
5.1.7 06 Mar 2025 H1 M3 L4 U21 BSD-3-Clause Yes Details →
5.2.0b1 19 Feb 2025 C1 H3 M6 L5 U32 BSD-3-Clause No Details →
5.1.6 05 Feb 2025 H1 M3 L4 U22 BSD-3-Clause Yes Details →
5.0.12 05 Feb 2025 H1 M4 L4 U13 BSD-3-Clause Yes Details →
4.2.19 05 Feb 2025 H3 M5 L5 U34 BSD-3-Clause Yes Details →
5.2.0a1 16 Jan 2025 C1 H3 M6 L5 U32 BSD-3-Clause No Details →
5.0.11 14 Jan 2025 H1 M4 L4 U13 BSD-3-Clause Yes Details →
5.1.5 14 Jan 2025 H1 M3 L4 U22 BSD-3-Clause Yes Details →
4.2.18 14 Jan 2025 H3 M5 L5 U34 BSD-3-Clause Yes Details →
4.2.17 04 Dec 2024 H3 M5 L5 U35 BSD-3-Clause Yes Details →
5.0.10 04 Dec 2024 H1 M4 L4 U14 BSD-3-Clause Yes Details →
5.1.4 04 Dec 2024 H1 M4 L4 U23 BSD-3-Clause Yes Details →
5.1.3 05 Nov 2024 H1 M5 L4 U25 BSD-3-Clause Yes Details →
5.1.2 08 Oct 2024 H1 M5 L4 U25 BSD-3-Clause Yes Details →
4.2.16 03 Sep 2024 H3 M5 L5 U37 BSD-3-Clause Yes Details →
5.0.9 03 Sep 2024 H2 M4 L4 U16 BSD-3-Clause Yes Details →
5.1.1 03 Sep 2024 H1 M5 L4 U25 BSD-3-Clause Yes Details →
5.1.0 07 Aug 2024 H2 M7 L4 U26 BSD-3-Clause No Details →
5.0.8 06 Aug 2024 H2 M4 L4 U18 BSD-3-Clause Yes Details →
4.2.15 06 Aug 2024 H3 M5 L5 U39 BSD-3-Clause Yes Details →
5.1.0rc1 24 Jul 2024 H2 M6 L4 U26 BSD-3-Clause No Details →
5.0.7 09 Jul 2024 C1 H2 M7 L4 U22 BSD-3-Clause Yes Details →
4.2.14 09 Jul 2024 H3 M5 L5 U43 BSD-3-Clause Yes Details →
5.1.0b1 26 Jun 2024 H2 M6 L4 U26 BSD-3-Clause No Details →
5.1.0a1 22 May 2024 H2 M6 L4 U26 BSD-3-Clause No Details →
4.2.13 07 May 2024 H4 M5 L5 U47 BSD-3-Clause Yes Details →
5.0.6 07 May 2024 C1 H4 M8 L4 U26 BSD-3-Clause Yes Details →
5.0.5 06 May 2024 C1 H4 M8 L4 U26 BSD-3-Clause Yes Details →
4.2.12 06 May 2024 H4 M5 L5 U47 BSD-3-Clause Yes Details →
5.0.4 03 Apr 2024 C1 H4 M8 L4 U26 BSD-3-Clause Yes Details →
5.0.3 04 Mar 2024 C1 H4 M8 L4 U26 BSD-3-Clause Yes Details →
4.2.11 04 Mar 2024 H4 M5 L5 U47 BSD-3-Clause Yes Details →
3.2.25 04 Mar 2024 H2 M3 L4 U12 BSD-3-Clause Yes Details →
3.2.24 06 Feb 2024 H2 M4 L4 U13 BSD-3-Clause Yes Details →
4.2.10 06 Feb 2024 H4 M5 L5 U48 BSD-3-Clause Yes Details →
5.0.2 06 Feb 2024 C1 H4 M8 L4 U27 BSD-3-Clause Yes Details →
5.0.1 02 Jan 2024 C1 H4 M8 L4 U28 BSD-3-Clause Yes Details →
4.2.9 02 Jan 2024 H4 M5 L5 U49 BSD-3-Clause Yes Details →
5.0.0 04 Dec 2023 C1 H5 M8 L4 U27 BSD-3-Clause No Details →
4.2.8 04 Dec 2023 H4 M5 L5 U49 BSD-3-Clause Yes Details →
5.0.0rc1 20 Nov 2023 C1 H4 M8 L4 U27 — No Details →
4.2.7 01 Nov 2023 H4 M5 L5 U49 — Yes Details →
4.1.13 01 Nov 2023 H2 M3 L4 U12 — Yes Details →
3.2.23 01 Nov 2023 H3 M4 L4 U14 — Yes Details →
5.0.0b1 23 Oct 2023 C1 H4 M8 L4 U27 — No Details →
3.2.22 04 Oct 2023 H4 M4 L4 U15 — Yes Details →
4.1.12 04 Oct 2023 H2 M3 L4 U13 — Yes Details →
4.2.6 04 Oct 2023 H4 M5 L5 U50 — Yes Details →
5.0.0a1 18 Sep 2023 C1 H4 M8 L4 U27 — No Details →
4.2.5 04 Sep 2023 H4 M5 L5 U51 — Yes Details →
4.1.11 04 Sep 2023 H2 M3 L4 U14 — Yes Details →
3.2.21 04 Sep 2023 H5 M4 L4 U16 — Yes Details →
4.2.4 01 Aug 2023 H4 M5 L5 U52 — Yes Details →
4.2.3 03 Jul 2023 H4 M5 L5 U52 — Yes Details →
4.1.10 03 Jul 2023 H2 M3 L4 U15 — Yes Details →
3.2.20 03 Jul 2023 H5 M5 L4 U17 — Yes Details →
4.2.2 05 Jun 2023 H4 M5 L5 U53 — Yes Details →
4.2.1 03 May 2023 H4 M5 L5 U53 — Yes Details →
4.1.9 03 May 2023 H2 M3 L4 U16 — Yes Details →
3.2.19 03 May 2023 H6 M5 L4 U18 — Yes Details →

The newest 120 of 438 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 1
  • 2008 2
  • 2009 2
  • 2010 1
  • 2011 14
  • 2012 4
  • 2013 6
  • 2014 9
  • 2015 14
  • 2016 7
  • 2017 3
  • 2018 17
  • 2019 35
  • 2020 12
  • 2021 19
  • 2022 70
  • 2023 14
  • 2024 27
  • 2025 27
  • 2026 64

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 76 of the 348 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for django

The 5 most severe of 348 vulnerabilities recorded for this package

Search all 348 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-0472: Code Injection in Django 9.8 critical 1.4.11 17 May 2022
CVE-2023-31047: Django Multiple File Upload Validation Bypass 9.8 critical 3.2.19 07 May 2023
CVE-2024-53908: Django SQL Injection Vulnerability in HasKey Lookup on Oracle 9.8 high 5.0.10 06 Dec 2024
CVE-2022-34265: Django Trunc() and Extract() Database Functions SQL Injection 9.8 critical 3.2.14 05 Jul 2022
CVE-2021-35042: SQL Injection in Django 9.8 critical 3.2.5 22 Sep 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About django

Is django safe to use?

Vulert records 348 vulnerabilities for django in PyPI: 16 critical, 66 high, 63 medium and 17 low, plus 186 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is django's Vulert package health score?

Vulert scores django 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of django affected?

Yes. 6.1.2, the version you would install today, has 10 known vulnerabilities, and 6 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of django should I use?

6.1.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does django have?

348 vulnerabilities are recorded for django in the PyPI ecosystem: 16 critical, 66 high, 63 medium and 17 low, plus 186 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django vulnerabilities disclosed?

76 vulnerabilities were recorded for django in the last 12 months, and the oldest entry in this database dates to 30 Oct 2007. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of django are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor django for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.