VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-filter: vulnerability history, versions and safety

django-filter is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 49 releases, from Sep 2020 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django-filter vulnerabilities

Vulert verdict on django-filter 26.2.0 i

Updated on 23 Oct 2026

Action needed: 26.2.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 26.2.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 29 Apr 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1,023 packages i
  • Stars 4,687 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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-filter, 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
26.2.0 03 Oct 2026 U1 non-standard Yes Details →
26.1.0 11 Jul 2026 U1 non-standard Yes Details →
25.2.0 05 Oct 2025 U1 non-standard Yes Details →
25.1.0 14 Feb 2025 U1 non-standard Yes Details →
24.3.0 02 Aug 2024 U1 non-standard Yes Details →
24.2.0 27 Mar 2024 U1 non-standard Yes Details →
24.1.0 08 Mar 2024 U1 non-standard Yes Details →
23.5.0 05 Dec 2023 U1 non-standard Yes Details →
23.4.0 20 Nov 2023 U1 non-standard Yes Details →
23.3.0 17 Sep 2023 U1 non-standard Yes Details →
23.2.0 30 Apr 2023 U1 non-standard Yes Details →
23.1.0 26 Mar 2023 U1 non-standard Yes Details →
22.1.0 17 Jun 2022 U1 non-standard Yes Details →
21.1.0 24 Sep 2021 U1 non-standard Yes Details →
2.4.0 27 Sep 2020 U1 non-standard Yes Details →
2.3.0 05 Jun 2020 H1 U1 non-standard Yes Details →
2.2.0 16 Jul 2019 H1 U1 non-standard Yes Details →
2.1.0 20 Jan 2019 H1 U1 non-standard Yes Details →
2.0.0 13 Jul 2018 H1 U1 non-standard Yes Details →
2.0.0.dev1 24 Oct 2017 H1 U1 non-standard Yes Details →
1.1.0 19 Oct 2017 H1 U1 non-standard Yes Details →
1.0.4 19 May 2017 H1 U1 non-standard Yes Details →
1.0.3 16 May 2017 H1 U1 non-standard Yes Details →
1.0.2 24 Mar 2017 H1 U1 non-standard Yes Details →
1.0.1 28 Nov 2016 H1 U1 non-standard Yes Details →
1.0.0 17 Nov 2016 H1 U1 non-standard Yes Details →
0.15.3 17 Oct 2016 H1 U1 non-standard Yes Details →
0.15.2 29 Sep 2016 H1 U1 non-standard Yes Details →
0.15.1 28 Sep 2016 H1 U1 non-standard Yes Details →
0.15.0 20 Sep 2016 H1 U1 non-standard Yes Details →
0.14.0 14 Aug 2016 H1 U1 non-standard Yes Details →
0.13.0 11 Mar 2016 H1 U1 non-standard Yes Details →
0.12.0 07 Jan 2016 H1 U1 non-standard Yes Details →
0.11.0 14 Aug 2015 H1 U1 non-standard Yes Details →
0.10.0 13 May 2015 H1 U1 non-standard Yes Details →
0.9.2 23 Jan 2015 H1 U1 non-standard Yes Details →
0.9.1 03 Dec 2014 H1 U1 non-standard Yes Details →
0.9.0 28 Nov 2014 H1 U1 non-standard Yes Details →
0.8.0 29 Sep 2014 H1 U1 non-standard Yes Details →
0.7.0 10 Aug 2013 H1 U1 non-standard Yes Details →
0.6.0 25 Mar 2013 H1 U1 non-standard Yes Details →
0.6.0a1 12 Mar 2013 H1 U1 non-standard Yes Details →
0.5.4 16 Nov 2012 H1 U1 non-standard Yes Details →
0.5.3 10 Mar 2010 H1 U1 non-standard Yes Details →
0.5.2 30 Nov 2009 H1 U1 non-standard Yes Details →
0.5.1 25 Aug 2009 H1 U1 non-standard Yes Details →
0.5.0 14 Aug 2009 H1 U1 non-standard Yes Details →
0.2.0 19 Jun 2009 H1 U1 non-standard Yes Details →
0.1.0 08 May 2009 H1 U1 non-standard Yes Details →

All 49 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for django-filter

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-15225: Potential DoS with NumberFilter conversion to integer values in django-filter 7.5 high 2.4.0 28 Sep 2020
CVE-2020-15225: django-filter Denial of Service Vulnerability N/A unrated 340cf7a23a2b3dcd7183f6a0d6c383e85b130d2b 29 Apr 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-filter

Is django-filter safe to use?

Vulert records 2 vulnerabilities for django-filter in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is django-filter's Vulert package health score?

Vulert scores django-filter 82/100, which reads as in good shape. 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).

Is the latest version of django-filter affected?

Yes. 26.2.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of django-filter should I use?

26.2.0 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-filter have?

2 vulnerabilities are recorded for django-filter in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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-filter vulnerabilities disclosed?

0 vulnerabilities were recorded for django-filter in the last 12 months, and the oldest entry in this database dates to 28 Sep 2020. 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-filter 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-filter for upcoming vulnerabilities?

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