Vulnerability Database · PyPI · Package report

django-tables2: vulnerability history, versions and safety

django-tables2 is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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.

Vulert verdict on django-tables2 3.0.1 i

Updated on 23 Oct 2026

Good news: 3.0.1, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 148 packages i
  • Stars 2,009 i
  • OpenSSF scorecard 2/10 i
  • Last release 1 month ago 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-tables2, 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
3.0.1 30 Aug 2026 none non-standard — Details →
3.0.0 13 Apr 2026 none non-standard — Details →
2.9.0 06 Apr 2026 none non-standard — Details →
2.8.0 21 Nov 2025 none non-standard — Details →
2.7.5 02 Jan 2025 none non-standard — Details →
2.7.4 23 Dec 2024 none non-standard — Details →
2.7.3 23 Dec 2024 none non-standard — Details →
2.7.2 23 Dec 2024 none non-standard — Details →
2.7.1 21 Dec 2024 none BSD-2-Clause — Details →
2.7.0 05 Dec 2023 none non-standard — Details →
2.6.0 27 Jun 2023 none non-standard — Details →
2.5.3 06 Mar 2023 none non-standard — Details →
2.5.2 07 Feb 2023 none non-standard — Details →
2.5.1 07 Jan 2023 none non-standard — Details →
2.5.0 27 Dec 2022 none non-standard — Details →
2.4.1 05 Oct 2021 none non-standard — Details →
2.4.0 15 May 2021 none non-standard — Details →
2.3.4 10 Jan 2021 none non-standard — Details →
2.3.3 29 Oct 2020 none non-standard — Details →
2.3.2 10 Oct 2020 none non-standard — Details →
2.3.1 02 Apr 2020 none non-standard — Details →
2.3.0 31 Mar 2020 none non-standard — Details →
2.2.1 21 Nov 2019 none non-standard — Details →
2.2.0 18 Nov 2019 none non-standard — Details →
2.1.1 23 Sep 2019 none non-standard — Details →
2.1.0 22 Jul 2019 none non-standard — Details →
2.0.6 26 Mar 2019 none non-standard — Details →
2.0.5 21 Feb 2019 none non-standard — Details →
2.0.4 21 Jan 2019 none non-standard — Details →
2.0.3 11 Nov 2018 none non-standard — Details →
2.0.2 22 Oct 2018 none non-standard — Details →
2.0.1 13 Sep 2018 none non-standard — Details →
2.0.0 13 Sep 2018 none non-standard — Details →
2.0.0b5 29 Aug 2018 none non-standard — Details →
2.0.0b4 29 Aug 2018 none non-standard — Details →
2.0.0b3 27 Aug 2018 none non-standard — Details →
2.0.0b2 27 Aug 2018 none non-standard — Details →
2.0.0b1 24 Aug 2018 none non-standard — Details →
2.0.0a5 28 Jul 2018 none non-standard — Details →
2.0.0a4 17 Jul 2018 none non-standard — Details →
2.0.0a3 24 May 2018 none non-standard — Details →
2.0.0a2 13 Apr 2018 none non-standard — Details →
2.0.0a1 12 Apr 2018 none non-standard — Details →
2.0.0a0 10 Apr 2018 none non-standard — Details →
1.21.2 03 Apr 2018 none non-standard — Details →
1.21.1 12 Mar 2018 none non-standard — Details →
1.21.0 12 Mar 2018 none non-standard — Details →
1.20.0 08 Mar 2018 none non-standard — Details →
1.19.0 02 Feb 2018 none non-standard — Details →
1.18.0 27 Jan 2018 none non-standard — Details →
1.17.1 14 Dec 2017 none non-standard — Details →
1.17.0 14 Dec 2017 none non-standard — Details →
1.16.0 27 Nov 2017 none non-standard — Details →
1.15.0 23 Nov 2017 none non-standard — Details →
1.14.2 30 Oct 2017 none non-standard — Details →
1.14.1 30 Oct 2017 none non-standard — Details →
1.14.0 30 Oct 2017 none non-standard — Details →
1.13.0 17 Oct 2017 none non-standard — Details →
1.12.0 10 Oct 2017 none non-standard — Details →
1.11.0 15 Sep 2017 none non-standard — Details →
1.10.0 30 Jun 2017 none non-standard — Details →
1.9.1 29 Jun 2017 none non-standard — Details →
1.9.0 22 Jun 2017 none non-standard — Details →
1.8.0 17 Jun 2017 none non-standard — Details →
1.7.1 02 Jun 2017 none non-standard — Details →
1.7.0 01 Jun 2017 none non-standard — Details →
1.6.1 08 May 2017 none non-standard — Details →
1.6.0 01 May 2017 none non-standard — Details →
1.5.0 18 Apr 2017 none non-standard — Details →
1.4.2 06 Mar 2017 none non-standard — Details →
1.4.1 27 Feb 2017 none non-standard — Details →
1.4.0 27 Feb 2017 none non-standard — Details →
1.3.0 20 Jan 2017 none non-standard — Details →
1.2.9 21 Dec 2016 none non-standard — Details →
1.2.8 21 Dec 2016 none non-standard — Details →
1.2.7 12 Dec 2016 none non-standard — Details →
1.2.6 06 Sep 2016 none non-standard — Details →
1.2.5 30 Jul 2016 none non-standard — Details →
1.2.4 28 Jul 2016 none non-standard — Details →
1.2.3 05 Jul 2016 none non-standard — Details →
1.2.2 04 Jun 2016 none non-standard — Details →
1.2.1 09 May 2016 none non-standard — Details →
1.2.0 02 May 2016 none non-standard — Details →
1.1.8 02 May 2016 none non-standard — Details →
1.1.7 26 Apr 2016 none non-standard — Details →
1.1.6 02 Apr 2016 none non-standard — Details →
1.1.5 02 Apr 2016 none non-standard — Details →
1.1.4 22 Mar 2016 none non-standard — Details →
1.1.3 21 Mar 2016 none non-standard — Details →
1.1.2 16 Feb 2016 none non-standard — Details →
1.1.1 26 Jan 2016 none non-standard — Details →
1.1.0 19 Jan 2016 none non-standard — Details →
1.0.7 03 Jan 2016 none non-standard — Details →
1.0.6 29 Dec 2015 none non-standard — Details →
1.0.5 17 Dec 2015 none non-standard — Details →
1.0.4 09 May 2015 none non-standard — Details →
1.0.3 09 May 2015 none non-standard — Details →
1.0.2 09 May 2015 none non-standard — Details →
1.0.1 09 May 2015 none non-standard — Details →
1.0.0 09 May 2015 none non-standard — Details →
0.16.0 07 Apr 2015 none — — Details →
0.15.0 02 Feb 2014 none — — Details →
0.14.0 18 Aug 2013 none — — Details →
0.13.0 15 Oct 2012 none — — Details →
0.12.1 15 Oct 2012 none — — Details →
0.12.0 18 Sep 2012 none — — Details →
0.11.0 03 May 2012 none — — Details →
0.10.4 10 Apr 2012 none — — Details →
0.10.3 05 Apr 2012 none — — Details →
0.10.2 26 Mar 2012 none — — Details →
0.10.1 26 Mar 2012 none — — Details →
0.10.0 14 Mar 2012 none — — Details →
0.9.6 08 Mar 2012 none — — Details →
0.9.5 08 Mar 2012 none — — Details →
0.9.4 01 Mar 2012 none — — Details →
0.9.3 22 Feb 2012 none — — Details →
0.9.2 22 Feb 2012 none — — Details →
0.9.1 21 Feb 2012 none — — Details →
0.8.4 07 Feb 2012 none — — Details →
0.8.3 07 Feb 2012 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for django-tables2

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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

Is django-tables2 safe to use?

Vulert has no vulnerabilities on record for django-tables2 in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

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

Vulert scores django-tables2 80/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-tables2 affected?

No. 3.0.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-tables2 should I use?

3.0.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-tables2 have?

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

How often are new django-tables2 vulnerabilities disclosed?

0 vulnerabilities were recorded for django-tables2 in the last 12 months. 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-tables2 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-tables2 for upcoming vulnerabilities?

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