VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

click: vulnerability history, versions and safety

click is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 60 releases, first recorded in Apr 2026. 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 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 30 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all click vulnerabilities

Vulert verdict on click 8.5.0 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 8.5.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 30 Apr 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 140,449 packages i
  • Stars 17,795 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 click, 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
8.5.0 26 Aug 2026 none BSD-3-Clause — Details →
8.4.2 24 Jun 2026 none BSD-3-Clause — Details →
8.4.1 22 May 2026 none BSD-3-Clause — Details →
8.4.0 17 May 2026 none BSD-3-Clause — Details →
8.3.3 22 Apr 2026 none BSD-3-Clause — Details →
8.3.2 03 Apr 2026 U1 BSD-3-Clause Yes Details →
8.3.1 15 Nov 2025 U1 BSD-3-Clause Yes Details →
8.3.0 18 Sep 2025 U1 BSD-3-Clause Yes Details →
8.2.2 02 Aug 2025 U1 BSD-3-Clause Yes Details →
8.2.1 20 May 2025 U1 BSD-3-Clause Yes Details →
8.2.0 10 May 2025 U1 BSD-3-Clause Yes Details →
8.1.8 21 Dec 2024 U1 non-standard Yes Details →
8.1.7 17 Aug 2023 U1 BSD-3-Clause Yes Details →
8.1.6 18 Jul 2023 U1 BSD-3-Clause Yes Details →
8.1.5 13 Jul 2023 U1 BSD-3-Clause Yes Details →
8.1.4 06 Jul 2023 U1 BSD-3-Clause Yes Details →
8.1.3 28 Apr 2022 U1 BSD-3-Clause Yes Details →
8.1.2 31 Mar 2022 U1 BSD-3-Clause Yes Details →
8.1.1 30 Mar 2022 U1 BSD-3-Clause Yes Details →
8.1.0 28 Mar 2022 U1 BSD-3-Clause Yes Details →
8.0.4 18 Feb 2022 U1 BSD-3-Clause Yes Details →
8.0.3 10 Oct 2021 U1 BSD-3-Clause Yes Details →
8.0.2 08 Oct 2021 U1 BSD-3-Clause Yes Details →
8.0.1 19 May 2021 U1 BSD-3-Clause Yes Details →
8.0.0 11 May 2021 U1 BSD-3-Clause Yes Details →
8.0.0rc1 16 Apr 2021 U1 BSD-3-Clause Yes Details →
8.0.0a1 25 Nov 2020 U1 BSD-3-Clause Yes Details →
7.1.2 27 Apr 2020 U1 BSD-3-Clause Yes Details →
7.1.1 09 Mar 2020 U1 BSD-3-Clause Yes Details →
7.1.0 09 Mar 2020 U1 BSD-3-Clause Yes Details →
7.0.0 25 Sep 2018 U1 non-standard Yes Details →
6.7.0 06 Jan 2017 U1 non-standard Yes Details →
6.7.0.dev0 06 Jan 2017 U1 non-standard Yes Details →
6.6.0 21 Nov 2016 U1 non-standard Yes Details →
6.5.0 04 Apr 2016 U1 non-standard Yes Details →
6.4.0 23 Mar 2016 U1 non-standard Yes Details →
6.3.0 22 Feb 2016 U1 non-standard Yes Details →
6.2.0 27 Nov 2015 U1 non-standard Yes Details →
6.1.0 27 Nov 2015 U1 non-standard Yes Details →
6.0.0 24 Nov 2015 U1 non-standard Yes Details →
5.1.0 17 Aug 2015 U1 non-standard Yes Details →
5.0.0 16 Aug 2015 U1 non-standard Yes Details →
4.1.0 14 Jul 2015 U1 non-standard Yes Details →
4.0.0 31 Mar 2015 U1 non-standard Yes Details →
3.3.0 07 Sep 2014 U1 non-standard Yes Details →
3.2.0 22 Aug 2014 U1 non-standard Yes Details →
3.1.0 13 Aug 2014 U1 non-standard Yes Details →
3.0.0 12 Aug 2014 U1 non-standard Yes Details →
2.6.0 11 Aug 2014 U1 non-standard Yes Details →
2.5.0 27 Jul 2014 U1 non-standard Yes Details →
2.4.0 04 Jul 2014 U1 non-standard Yes Details →
2.3.0 03 Jul 2014 U1 non-standard Yes Details →
2.2.0 26 Jun 2014 U1 non-standard Yes Details →
2.1.0 14 Jun 2014 U1 non-standard Yes Details →
2.0.0 06 Jun 2014 U1 non-standard Yes Details →
1.1.0 23 May 2014 U1 non-standard Yes Details →
1.0.0 21 May 2014 U1 non-standard Yes Details →
0.7.0 11 May 2014 U1 non-standard Yes Details →
0.6.0 07 May 2014 U1 non-standard Yes Details →
0.5.1 06 May 2014 U1 non-standard Yes Details →
0.5.0 06 May 2014 U1 non-standard Yes Details →
0.4.0 06 May 2014 U1 non-standard Yes Details →
0.3.0 06 May 2014 U1 non-standard Yes Details →
0.2.0 05 May 2014 U1 non-standard Yes Details →
0.1.0 28 Apr 2014 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for click

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-7246: Command Injection Vulnerability in Pallets Click 7.2 high 8.3.3 30 Apr 2026

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 click

Is click safe to use?

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

Vulert scores click 90/100, which reads as healthy. 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 click affected?

No. 8.5.0, 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 click should I use?

8.5.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 click have?

1 vulnerability is recorded for click in the PyPI ecosystem: 0 critical, 0 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 click vulnerabilities disclosed?

1 vulnerability was recorded for click in the last 12 months, and the oldest entry in this database dates to 30 Apr 2026. 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 click 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 click for upcoming vulnerabilities?

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