VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-select2: vulnerability history, versions and safety

django-select2 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 101 releases, from May 2025 to Jul 2026. 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
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django-select2 vulnerabilities

Vulert verdict on django-select2 8.6.1 i

Updated on 23 Oct 2026

Good news: 8.6.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 8.6.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.6.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.6.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 48 packages i
  • Stars 206 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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-select2, 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
8.6.1 15 Oct 2026 none MIT — Details →
8.6.0 10 Oct 2026 none MIT — Details →
8.5.0 10 Oct 2026 none MIT — Details →
8.4.8 07 Jan 2026 none MIT — Details →
8.4.7 18 Dec 2025 none MIT — Details →
8.4.6 18 Dec 2025 none MIT — Details →
8.4.5 16 Dec 2025 none MIT — Details →
8.4.4 15 Dec 2025 none MIT — Details →
8.4.3 15 Oct 2025 none MIT — Details →
8.4.2 15 Oct 2025 none MIT — Details →
8.2.4 09 Jun 2025 U1 MIT Yes Details →
8.4.1 26 May 2025 none MIT — Details →
8.4.0 15 Mar 2025 H1 U1 MIT Yes Details →
8.3.0 09 Feb 2025 H1 U1 MIT Yes Details →
8.2.3 10 Dec 2024 H1 U1 MIT Yes Details →
8.2.2 10 Dec 2024 H1 U1 MIT Yes Details →
8.2.1 09 Aug 2024 H1 U1 MIT Yes Details →
8.2.0 29 Jun 2024 H1 U1 MIT Yes Details →
8.1.2 23 May 2023 H1 U1 MIT Yes Details →
8.1.1 10 Mar 2023 H1 U1 MIT Yes Details →
8.1.0 08 Feb 2023 H1 U1 MIT Yes Details →
8.0.0 05 Nov 2022 H1 U1 MIT Yes Details →
7.11.1 03 Nov 2022 H1 U1 MIT Yes Details →
7.11.0 30 Oct 2022 H1 U1 MIT Yes Details →
7.10.1 09 Sep 2022 H1 U1 MIT Yes Details →
7.10.0 03 Feb 2022 H1 U1 MIT Yes Details →
7.9.0 05 Nov 2021 H1 U1 MIT Yes Details →
7.8.1 03 Nov 2021 H1 U1 MIT Yes Details →
7.7.3 02 Oct 2021 H1 U1 MIT Yes Details →
7.7.2 22 Sep 2021 H1 U1 MIT Yes Details →
7.7.1 13 Apr 2021 H1 U1 MIT Yes Details →
7.7.0 30 Mar 2021 H1 U1 MIT Yes Details →
7.6.2 09 Mar 2021 H1 U1 MIT Yes Details →
7.6.1 16 Jan 2021 H1 U1 MIT Yes Details →
7.6.0 09 Jan 2021 H1 U1 MIT Yes Details →
7.5.0 15 Dec 2020 H1 U1 MIT Yes Details →
7.4.2 24 May 2020 H1 U1 MIT Yes Details →
7.4.1 24 May 2020 H1 U1 MIT Yes Details →
7.3.0 23 May 2020 H1 U1 MIT Yes Details →
7.2.4 15 May 2020 H1 U1 MIT Yes Details →
7.2.3 20 Mar 2020 H1 U1 MIT Yes Details →
7.2.2 13 Mar 2020 H1 U1 MIT Yes Details →
7.2.0 05 Jan 2020 H1 U1 MIT Yes Details →
7.1.2 21 Nov 2019 H1 U1 MIT Yes Details →
7.1.1 26 Aug 2019 H1 U1 MIT Yes Details →
7.1.0 09 Jul 2019 H1 U1 MIT Yes Details →
7.0.5 10 Jun 2019 H1 U1 MIT Yes Details →
7.0.4 10 Jun 2019 H1 U1 MIT Yes Details →
7.0.3 10 Apr 2019 H1 U1 MIT Yes Details →
7.0.2 08 Apr 2019 H1 U1 MIT Yes Details →
6.3.1 23 Aug 2018 H1 U1 Apache-2.0 Yes Details →
6.3.0 22 Aug 2018 H1 U1 Apache-2.0 Yes Details →
6.2.0 18 Aug 2018 H1 U1 Apache-2.0 Yes Details →
6.1.2 05 Aug 2018 H1 U1 Apache-2.0 Yes Details →
6.1.1 24 Jul 2018 H1 U1 Apache-2.0 Yes Details →
6.1.0 30 Jun 2018 H1 U1 Apache-2.0 Yes Details →
6.0.3 14 Jun 2018 H1 U1 Apache-2.0 Yes Details →
6.0.2 17 Feb 2018 H1 U1 Apache-2.0 Yes Details →
6.0.1 10 Jan 2018 H1 U1 Apache-2.0 Yes Details →
6.0.0 25 Nov 2017 H1 U1 Apache-2.0 Yes Details →
5.11.1 24 Jul 2017 H1 U1 non-standard Yes Details →
5.11.0 16 Jul 2017 H1 U1 non-standard Yes Details →
5.10.0 18 Apr 2017 H1 U1 non-standard Yes Details →
5.9.0 14 Apr 2017 H1 U1 non-standard Yes Details →
5.8.10 05 Dec 2016 H1 U1 non-standard Yes Details →
5.8.9 15 Aug 2016 H1 U1 non-standard Yes Details →
5.8.7 14 Aug 2016 H1 U1 non-standard Yes Details →
5.8.6 19 Jun 2016 H1 U1 non-standard Yes Details →
5.8.5 23 May 2016 H1 U1 non-standard Yes Details →
5.8.4 10 Mar 2016 H1 U1 non-standard Yes Details →
5.8.3 08 Mar 2016 H1 U1 non-standard Yes Details →
5.8.2 01 Mar 2016 H1 U1 non-standard Yes Details →
5.8.1 24 Feb 2016 H1 U1 non-standard Yes Details →
5.8.0 08 Feb 2016 H1 U1 non-standard Yes Details →
5.7.1 27 Jan 2016 H1 U1 non-standard Yes Details →
5.7.0 26 Jan 2016 H1 U1 non-standard Yes Details →
5.6.0 19 Jan 2016 H1 U1 non-standard Yes Details →
5.5.0 15 Dec 2015 H1 U1 non-standard Yes Details →
5.4.3 10 Dec 2015 H1 U1 non-standard Yes Details →
5.4.2 01 Dec 2015 H1 U1 non-standard Yes Details →
5.4.1 30 Nov 2015 H1 U1 non-standard Yes Details →
5.4.0 23 Nov 2015 H1 U1 non-standard Yes Details →
5.3.1 17 Nov 2015 H1 U1 non-standard Yes Details →
5.3.0 12 Nov 2015 H1 U1 non-standard Yes Details →
5.2.1 27 Oct 2015 H1 U1 non-standard Yes Details →
5.2.0 05 Oct 2015 H1 U1 non-standard Yes Details →
5.1.1 05 Oct 2015 H1 U1 non-standard Yes Details →
5.1.0 01 Oct 2015 H1 U1 non-standard Yes Details →
5.0.3 30 Sep 2015 H1 U1 non-standard Yes Details →
5.0.2 29 Sep 2015 H1 U1 non-standard Yes Details →
5.0.1 29 Sep 2015 H1 U1 non-standard Yes Details →
4.3.2 25 Sep 2015 H1 U1 non-standard Yes Details →
4.3.1 29 Apr 2015 H1 U1 non-standard Yes Details →
4.3.0 27 Apr 2015 H1 U1 non-standard Yes Details →
4.2.2 05 Nov 2013 H1 U1 non-standard Yes Details →
4.2.1 17 Sep 2013 H1 U1 non-standard Yes Details →
4.2.0 15 Sep 2013 H1 U1 non-standard Yes Details →
4.0.0 15 Mar 2013 H1 U1 non-standard Yes Details →
3.3.1 13 Mar 2013 H1 U1 non-standard Yes Details →
3.3.0 02 Mar 2013 H1 U1 non-standard Yes Details →
3.2.1 19 Jan 2013 H1 U1 — Yes Details →
3.2.0 13 Jan 2013 H1 U1 — Yes Details →
3.1.5 18 Dec 2012 H1 U1 — Yes Details →
3.1.4 28 Nov 2012 H1 U1 — Yes Details →
3.1.3 26 Nov 2012 H1 U1 — Yes Details →
3.1.2 04 Oct 2012 H1 U1 — Yes Details →
3.1.1 28 Sep 2012 H1 U1 — Yes Details →
3.1.0 28 Sep 2012 H1 U1 — Yes Details →
3.0.2 14 Sep 2012 H1 U1 — Yes Details →
3.0.1 03 Sep 2012 H1 U1 — Yes Details →
3.0.0 31 Aug 2012 H1 U1 — Yes Details →
2.0.1 24 Aug 2012 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for django-select2

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48383: django-select2 Vulnerable to Widget Instance Secret Cache Key Leaking 8.2 high 8.4.1 27 May 2025
CVE-2025-48383: django-select2 Widget Instance Secret Cache Key Leaking Vulnerability 8.2 high 8.4.1 07 Jul 2026

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-select2

Is django-select2 safe to use?

Vulert records 2 vulnerabilities for django-select2 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-select2's Vulert package health score?

Vulert scores django-select2 72/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-select2 affected?

No. 8.6.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of django-select2 should I use?

8.6.1 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-select2 have?

2 vulnerabilities are recorded for django-select2 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-select2 vulnerabilities disclosed?

1 vulnerability was recorded for django-select2 in the last 12 months, and the oldest entry in this database dates to 27 May 2025. 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-select2 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-select2 for upcoming vulnerabilities?

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