VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-tomselect: vulnerability history, versions and safety

django-tomselect is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 31 releases, first recorded in Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
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-tomselect vulnerabilities

Vulert verdict on django-tomselect 2026.6.2 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release 2026.6.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Mar 2025 i
  • Highest CVSS 1.7 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 88 i
  • Last release 4 months ago 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-tomselect, 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
2026.6.2 13 Jun 2026 none MIT — Details →
2026.6.1 09 Jun 2026 none MIT — Details →
2026.5.6 31 May 2026 none MIT — Details →
2026.5.5 26 May 2026 none MIT — Details →
2026.5.4 24 May 2026 none MIT — Details →
2026.5.3 21 May 2026 none MIT — Details →
2026.5.2 14 May 2026 none MIT — Details →
2026.5.1 07 May 2026 none MIT — Details →
2026.4.1 08 Apr 2026 none MIT — Details →
2026.3.3 17 Mar 2026 none MIT — Details →
2026.3.2 16 Mar 2026 none MIT — Details →
2026.3.1 15 Mar 2026 none MIT — Details →
2026.1.3 29 Jan 2026 none MIT — Details →
2026.1.2 21 Jan 2026 none MIT — Details →
2026.1.1 19 Jan 2026 none MIT — Details →
2025.9.1 09 Sep 2025 none MIT — Details →
2025.7.1 01 Jul 2025 none MIT — Details →
2025.5.7 23 May 2025 none MIT — Details →
2025.5.6 23 May 2025 none MIT — Details →
2025.5.5 23 May 2025 none MIT — Details →
2025.5.4 13 May 2025 none MIT — Details →
2025.5.3 12 May 2025 none MIT — Details →
2025.5.2 12 May 2025 none MIT — Details →
2025.5.1 03 May 2025 none MIT — Details →
2025.3.4 28 Mar 2025 none MIT — Details →
2025.3.3 26 Mar 2025 none MIT — Details →
2025.3.2 26 Mar 2025 L1 MIT Yes Details →
2025.3.1 26 Mar 2025 L1 MIT Yes Details →
2025.2.3 19 Feb 2025 L1 MIT Yes Details →
2025.2.2 16 Feb 2025 L1 MIT Yes Details →
2025.2.1 16 Feb 2025 L1 MIT Yes Details →
2025.1.2 05 Jan 2025 L1 MIT Yes Details →
2025.1.1 03 Jan 2025 L1 MIT Yes Details →
2024.12.7 27 Dec 2024 L1 MIT Yes Details →
2024.12.6 27 Dec 2024 L1 MIT Yes Details →
2024.12.5 26 Dec 2024 L1 MIT Yes Details →
2024.12.4 26 Dec 2024 L1 MIT Yes Details →
2024.12.3 26 Dec 2024 L1 MIT Yes Details →
2024.12.2 16 Dec 2024 L1 MIT Yes Details →
2024.12.1 16 Dec 2024 L1 MIT Yes Details →
0.5.1b11 06 Mar 2024 L1 MIT Yes Details →
0.5.1b10 03 Nov 2023 L1 MIT Yes Details →
0.5.1b9 03 Nov 2023 L1 MIT Yes Details →
0.5.1b8 02 Nov 2023 L1 MIT Yes Details →
0.5.1b7 01 Nov 2023 L1 MIT Yes Details →
0.5.1b6 17 Oct 2023 L1 MIT Yes Details →
0.5.1b5 12 Oct 2023 L1 MIT Yes Details →
0.5.1b4 12 Oct 2023 L1 MIT Yes Details →
0.5.1b3 11 Oct 2023 L1 MIT Yes Details →
0.5.1b2 11 Oct 2023 L1 MIT Yes Details →
0.5.1b1 10 Oct 2023 L1 MIT Yes Details →
0.5.1b0 10 Oct 2023 L1 MIT Yes Details →
0.4.4 10 Oct 2023 L1 MIT Yes Details →
0.4.3 04 Jul 2023 L1 MIT Yes Details →
0.4.2 03 Jul 2023 L1 MIT Yes Details →
0.4.1 03 Jul 2023 L1 MIT Yes Details →
0.4.0 02 Jul 2023 L1 MIT Yes Details →

All 57 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

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

03 Vulnerabilities

Recorded vulnerabilities for django-tomselect

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Inadequate Escaping of Dangerous Characters in Django TomSelect Package 1.7 low 2025.3.3 26 Mar 2025

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

Is django-tomselect safe to use?

Vulert records 1 vulnerabilities for django-tomselect in PyPI: 0 critical, 0 high, 0 medium and 1 low. 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-tomselect's Vulert package health score?

Vulert scores django-tomselect 75/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-tomselect affected?

No. 2026.6.2, 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-tomselect should I use?

2026.6.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-tomselect have?

1 vulnerability is recorded for django-tomselect in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django-tomselect vulnerabilities disclosed?

0 vulnerabilities were recorded for django-tomselect in the last 12 months, and the oldest entry in this database dates to 26 Mar 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-tomselect 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-tomselect for upcoming vulnerabilities?

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