VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

channels: vulnerability history, versions and safety

channels is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 3 releases, from Feb 2021 to Mar 2021. 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
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 channels vulnerabilities

Vulert verdict on channels 4.3.2 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 4.3.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 19 Mar 2021 i
  • Highest CVSS 7.4 i
  • With no published fix 0 i
  • Depended on by 256 packages i
  • Stars 6,364 i
  • OpenSSF scorecard 3/10 i
  • Last release 11 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 channels, 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
4.3.2 20 Nov 2025 none non-standard — Details →
4.3.1 01 Aug 2025 none non-standard — Details →
4.3.0 28 Jul 2025 none non-standard — Details →
4.2.2 30 Mar 2025 none non-standard — Details →
4.2.1 29 Mar 2025 none non-standard — Details →
4.2.0 15 Nov 2024 none non-standard — Details →
4.1.0 03 Apr 2024 none non-standard — Details →
4.0.0 15 Oct 2022 none non-standard — Details →
4.0.0b1 25 Aug 2022 none non-standard — Details →
3.0.5 24 Jun 2022 none non-standard — Details →
3.0.4 11 Jul 2021 none non-standard — Details →
3.0.3 28 Dec 2020 none non-standard — Details →
3.0.2 09 Nov 2020 H1 U1 non-standard Yes Details →
3.0.1 04 Nov 2020 H1 U1 non-standard Yes Details →
3.0.0 30 Oct 2020 H1 U1 non-standard Yes Details →
2.4.0 18 Dec 2019 none non-standard — Details →
2.3.1 23 Oct 2019 none non-standard — Details →
2.3.0 18 Sep 2019 none non-standard — Details →
2.2.0 14 Apr 2019 none non-standard — Details →
2.1.7 01 Feb 2019 none non-standard — Details →
2.1.6 09 Dec 2018 none non-standard — Details →
2.1.5 22 Oct 2018 none non-standard — Details →
2.1.4 19 Oct 2018 none non-standard — Details →
2.1.3 17 Aug 2018 none non-standard — Details →
2.1.2 13 Jun 2018 none non-standard — Details →
2.1.1 18 Apr 2018 none non-standard — Details →
2.1.0 12 Apr 2018 none non-standard — Details →
2.0.2 08 Feb 2018 none non-standard — Details →
2.0.1 06 Feb 2018 none non-standard — Details →
2.0.0 02 Feb 2018 none non-standard — Details →
1.1.8 15 Sep 2017 none non-standard — Details →
1.1.7 14 Sep 2017 none non-standard — Details →
1.1.6 28 Jun 2017 none non-standard — Details →
1.1.5 16 Jun 2017 none non-standard — Details →
1.1.4 15 Jun 2017 none non-standard — Details →
1.1.3 07 Apr 2017 none non-standard — Details →
1.1.2 01 Apr 2017 none non-standard — Details →
1.1.1 19 Mar 2017 none non-standard — Details →
1.1.0 18 Mar 2017 none non-standard — Details →
1.0.3 01 Feb 2017 none non-standard — Details →
1.0.2 12 Jan 2017 none non-standard — Details →
1.0.1 10 Jan 2017 none non-standard — Details →
1.0.0 09 Jan 2017 none non-standard — Details →
0.17.3 12 Oct 2016 none non-standard — Details →
0.17.2 04 Aug 2016 none non-standard — Details →
0.17.1 23 Jul 2016 none non-standard — Details →
0.17.0 19 Jul 2016 none non-standard — Details →
0.16.1 12 Jul 2016 none non-standard — Details →
0.16.0 06 Jul 2016 none non-standard — Details →
0.15.1 29 Jun 2016 none non-standard — Details →
0.15.0 22 Jun 2016 none non-standard — Details →
0.14.3 21 Jun 2016 none non-standard — Details →
0.14.2 16 Jun 2016 none non-standard — Details →
0.14.1 10 Jun 2016 none non-standard — Details →
0.14.0 26 May 2016 none non-standard — Details →
0.13.1 13 May 2016 none non-standard — Details →
0.13.0 07 May 2016 none non-standard — Details →
0.12.0 26 Apr 2016 none non-standard — Details →
0.11.0 05 Apr 2016 none non-standard — Details →
0.10.3 29 Mar 2016 none non-standard — Details →
0.10.2 23 Mar 2016 none non-standard — Details →
0.10.1 22 Mar 2016 none non-standard — Details →
0.10.0 21 Mar 2016 none non-standard — Details →
0.9.5 11 Mar 2016 none non-standard — Details →
0.9.4 08 Mar 2016 none non-standard — Details →
0.9.3 29 Feb 2016 none non-standard — Details →
0.9.2 29 Feb 2016 none non-standard — Details →
0.9.1 21 Feb 2016 none non-standard — Details →
0.9.0 21 Feb 2016 none non-standard — Details →
0.8.0 10 Sep 2015 none non-standard — Details →
0.7.0 08 Sep 2015 none non-standard — Details →
0.1.1 15 Jun 2015 none non-standard — Details →
0.1.0 15 Jun 2015 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 channels

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35681: Django Channels - Exposure of Sensitive Information to an Unauthorized Actor 7.4 high 3.0.3 19 Mar 2021
CVE-2020-35681: Django Channels Information Leakage N/A unrated 3.0.3 22 Feb 2021

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 channels

Is channels safe to use?

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

Vulert scores channels 78/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 channels affected?

No. 4.3.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 channels should I use?

4.3.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 channels have?

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

0 vulnerabilities were recorded for channels in the last 12 months, and the oldest entry in this database dates to 22 Feb 2021. 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 channels 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 channels for upcoming vulnerabilities?

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