Vulnerability Database · PyPI · Package report

tendenci: vulnerability history, versions and safety

tendenci is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 120 releases, from Jun 2020 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
10 vulnerabilities recorded C1 M4 U5
i
5 with no fix published

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

See the unfixed vulnerabilities →
i
8 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.

Vulert verdict on tendenci 16.30.0 i

Updated on 23 Oct 2026

Careful: 16.30.0 has 5 known vulnerabilities, and 5 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 Niche
  • Community Quiet

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 16.30.0 — affected i
  • Vulnerabilities on record 10 over 6 years · 8 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Stars 556 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 tendenci, 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
16.30.0 15 Oct 2026 M2 U3 — No Details →
16.20.0 15 Sep 2026 M2 U3 — No Details →
16.16.0 05 Jul 2026 M2 U3 — No Details →
16.15.0 11 Jun 2026 M2 U3 — No Details →
16.14.0 29 May 2026 M2 U3 — No Details →
16.13.0 28 May 2026 M2 U3 — No Details →
16.12.0 28 May 2026 M2 U3 — No Details →
16.11.0 14 May 2026 M2 U3 — No Details →
16.1.0 16 Apr 2026 M2 U3 non-standard No Details →
16.0.0 31 Mar 2026 M2 U3 non-standard No Details →
15.3.12 19 Jan 2026 M1 U3 non-standard No Details →
15.3.11 08 Jan 2026 M2 U4 non-standard No Details →
15.3.10 28 Dec 2025 M2 U4 non-standard No Details →
15.3.9 12 Dec 2025 M2 U4 non-standard No Details →
15.3.8 09 Dec 2025 M2 U4 non-standard No Details →
15.3.7 14 Oct 2025 M3 U4 non-standard No Details →
15.3.6 09 Oct 2025 M3 U4 non-standard No Details →
15.3.5 03 Jul 2025 M3 U4 non-standard No Details →
15.3.4 07 May 2025 M3 U4 non-standard No Details →
15.3.3 10 Apr 2025 M3 U4 GPL-3.0 No Details →
15.3.2 24 Feb 2025 M3 U4 GPL-3.0 No Details →
15.3.1 02 Jan 2025 M3 U4 GPL-3.0 No Details →
15.3.0 21 Nov 2024 M3 U4 GPL-3.0 No Details →
15.2.1 27 Aug 2024 M3 U4 GPL-3.0 No Details →
15.2.0 25 Aug 2024 M3 U4 GPL-3.0 No Details →
15.1.0 22 May 2024 M3 U4 GPL-3.0 No Details →
15.0.0 30 Mar 2024 M3 U4 GPL-3.0 No Details →
14.8.2 21 Feb 2024 M3 U4 GPL-3.0 No Details →
14.8.1 25 Dec 2023 M3 U4 GPL-3.0 No Details →
14.8.0 10 Dec 2023 M3 U4 GPL-3.0 No Details →
14.5.1 04 Jul 2023 M3 U4 GPL-3.0 No Details →
14.5.0 28 Jun 2023 M3 U4 GPL-3.0 No Details →
14.4.0 17 May 2023 M3 U4 GPL-3.0 No Details →
14.3.6 28 Mar 2023 M3 U4 GPL-3.0 No Details →
14.3.5 10 Mar 2023 M3 U4 GPL-3.0 No Details →
14.3.4 09 Mar 2023 M3 U4 GPL-3.0 No Details →
14.3.3 21 Dec 2022 M3 U4 GPL-3.0 No Details →
14.3.2 19 Nov 2022 M3 U4 GPL-3.0 No Details →
14.3.1 01 Nov 2022 M3 U4 GPL-3.0 No Details →
14.3.0 26 Aug 2022 M3 U4 GPL-3.0 No Details →
14.2.0 11 Jul 2022 M3 U4 GPL-3.0 No Details →
14.1.1 11 Jul 2022 M3 U4 GPL-3.0 No Details →
14.1.0 18 Apr 2022 M3 U4 GPL-3.0 No Details →
14.0.4 04 Feb 2022 M3 U4 GPL-3.0 No Details →
14.0.3 17 Jan 2022 M3 U4 GPL-3.0 No Details →
14.0.2 13 Jan 2022 M3 U4 GPL-3.0 No Details →
14.0.1 02 Jan 2022 M3 U4 GPL-3.0 No Details →
14.0.0 15 Dec 2021 M3 U4 GPL-3.0 No Details →
12.5.11 24 Sep 2021 M3 U4 GPL-3.0 No Details →
12.5.10 08 Sep 2021 M3 U4 GPL-3.0 No Details →
12.5.9 07 Sep 2021 M3 U4 GPL-3.0 No Details →
12.5.8 11 Aug 2021 M3 U4 GPL-3.0 No Details →
12.5.7 20 Jul 2021 M3 U4 GPL-3.0 No Details →
12.5.6 01 Jul 2021 M3 U4 GPL-3.0 No Details →
12.5.5 24 Jun 2021 M3 U4 GPL-3.0 No Details →
12.5.4 22 Jun 2021 M3 U4 GPL-3.0 No Details →
12.5.3 11 Jun 2021 M3 U4 GPL-3.0 No Details →
12.5.2 02 Jun 2021 M3 U4 GPL-3.0 No Details →
12.5.1 07 May 2021 M3 U4 GPL-3.0 No Details →
12.5.0 07 May 2021 M3 U4 GPL-3.0 No Details →
12.4.13 22 Apr 2021 M3 U4 GPL-3.0 No Details →
12.4.12 07 Apr 2021 M3 U4 GPL-3.0 No Details →
12.4.11 07 Apr 2021 M3 U4 GPL-3.0 No Details →
12.4.10 31 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.9 31 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.8 23 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.7 10 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.6 03 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.5 01 Mar 2021 M3 U4 GPL-3.0 No Details →
12.4.4 24 Feb 2021 M3 U4 GPL-3.0 No Details →
12.4.3 09 Feb 2021 M3 U4 GPL-3.0 No Details →
12.4.2 05 Feb 2021 M3 U4 GPL-3.0 No Details →
12.4.1 04 Feb 2021 M3 U4 GPL-3.0 No Details →
12.4.0 12 Jan 2021 M3 U4 GPL-3.0 No Details →
12.3.3 17 Nov 2020 M3 U4 GPL-3.0 No Details →
12.3.2 29 Oct 2020 M3 U4 GPL-3.0 No Details →
12.3.1 29 Oct 2020 M4 U4 GPL-3.0 No Details →
12.3.0 26 Oct 2020 M4 U4 GPL-3.0 No Details →
12.2.8 01 Oct 2020 M4 U4 GPL-3.0 No Details →
12.2.7 30 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.6 28 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.5 26 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.4 26 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.3 23 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.2 17 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.1 09 Sep 2020 M4 U4 GPL-3.0 No Details →
12.2.0 06 Sep 2020 M4 U4 GPL-3.0 No Details →
12.1.1 21 Aug 2020 M4 U4 GPL-3.0 No Details →
12.1.0 14 Aug 2020 M4 U4 GPL-3.0 No Details →
12.0.14 10 Aug 2020 M4 U4 GPL-3.0 No Details →
12.0.13 07 Aug 2020 M4 U4 GPL-3.0 No Details →
12.0.12 30 Jul 2020 M4 U4 GPL-3.0 No Details →
12.0.11 24 Jun 2020 M4 U4 GPL-3.0 No Details →
12.0.10 17 Jun 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.9 12 Jun 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.8 01 Jun 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.7 13 May 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.6 10 May 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.5 01 May 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.4 29 Apr 2020 C1 M4 U5 GPL-3.0 No Details →
12.0.3 22 Apr 2020 C1 M4 U5 — No Details →
12.0.2 09 Apr 2020 C1 M4 U5 — No Details →
12.0.1 03 Apr 2020 C1 M4 U5 — No Details →
12.0.0 30 Mar 2020 C1 M4 U5 — No Details →
11.4.10 10 Feb 2020 C1 M4 U5 — No Details →
11.4.9 26 Jan 2020 C1 M4 U5 — No Details →
11.4.8 26 Jan 2020 C1 M4 U5 — No Details →
11.4.7 09 Jan 2020 C1 M4 U5 — No Details →
11.4.6 30 Dec 2019 C1 M4 U5 — No Details →
11.4.5 20 Dec 2019 C1 M4 U5 — No Details →
11.4.4 26 Nov 2019 C1 M4 U5 — No Details →
11.4.3 14 Nov 2019 C1 M4 U5 — No Details →
11.4.2 17 Oct 2019 C1 M4 U5 — No Details →
11.4.1 07 Oct 2019 C1 M4 U5 — No Details →
11.4.0 02 Oct 2019 C1 M4 U5 — No Details →
11.3.1 21 Aug 2019 C1 M4 U5 — No Details →
11.3.0 09 Aug 2019 C1 M4 U5 — No Details →
11.2.12 07 Aug 2019 C1 M4 U5 — No Details →
11.2.11 15 Jul 2019 C1 M4 U5 — No Details →
11.2.10 20 Jun 2019 C1 M4 U5 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2026 8

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

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 tendenci

Is tendenci safe to use?

Vulert records 10 vulnerabilities for tendenci in PyPI: 1 critical, 0 high, 4 medium and 0 low, plus 5 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is tendenci's Vulert package health score?

Vulert scores tendenci 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 tendenci affected?

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

Which version of tendenci should I use?

16.30.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 tendenci have?

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

8 vulnerabilities were recorded for tendenci in the last 12 months, and the oldest entry in this database dates to 21 Jun 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 tendenci 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 tendenci for upcoming vulnerabilities?

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