VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

collective-task: vulnerability history, versions and safety

collective-task is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 15 releases, first recorded in Dec 2022. 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 M1 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 collective-task vulnerabilities

Vulert verdict on collective-task 3.0.12 i

Updated on 23 Oct 2026

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

Package health score 64/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 3.0.12 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 15 Dec 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 4 i
  • Last release 39 months 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 collective-task, 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.12 20 Jul 2023 none non-standard — Details →
3.0.11 29 Mar 2023 none non-standard — Details →
3.0.10 19 Aug 2022 none non-standard — Details →
3.0.9 21 Jun 2022 U1 non-standard Yes Details →
3.0.8 13 May 2022 M1 U1 non-standard Yes Details →
3.0.7 09 Feb 2022 M1 U1 non-standard Yes Details →
3.0.6 20 Apr 2021 M1 U1 non-standard Yes Details →
3.0.5 09 Sep 2019 M1 U1 non-standard Yes Details →
3.0.4 08 Mar 2019 M1 U1 non-standard Yes Details →
3.0.3 22 Feb 2019 M1 U1 non-standard Yes Details →
3.0.2 22 Aug 2018 M1 U1 non-standard Yes Details →
3.0.1 30 Jul 2018 M1 U1 non-standard Yes Details →
3.0.0 30 May 2017 M1 non-standard Yes Details →
2.5.0 07 Dec 2016 M1 non-standard Yes Details →
2.3.0 15 Apr 2016 M1 non-standard Yes Details →
2.2.1 13 Jan 2016 M1 U1 non-standard Yes Details →
2.2.0 24 Nov 2015 M1 non-standard Yes Details →
2.1.0 30 Jun 2015 M1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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 collective-task

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-4527: collective-task Cross-site Scripting vulnerability 6.1 medium 3.0.9 15 Dec 2022
CVE-2022-4527: collective-task - Cross-Site Scripting (XSS) Vulnerability N/A unrated 1aac7f83fa2c2b41d59ba02748912953461f3fac 15 Dec 2022

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 collective-task

Is collective-task safe to use?

Vulert records 2 vulnerabilities for collective-task in PyPI: 0 critical, 0 high, 1 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 collective-task's Vulert package health score?

Vulert scores collective-task 64/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).

Is the latest version of collective-task affected?

No. 3.0.12, 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 collective-task should I use?

3.0.12 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 collective-task have?

2 vulnerabilities are recorded for collective-task in the PyPI ecosystem: 0 critical, 0 high, 1 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 collective-task vulnerabilities disclosed?

0 vulnerabilities were recorded for collective-task in the last 12 months, and the oldest entry in this database dates to 15 Dec 2022. 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 collective-task 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 collective-task for upcoming vulnerabilities?

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