VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cloudtoken: vulnerability history, versions and safety

cloudtoken is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 21 releases, from Aug 2018 to May 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 L1 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 cloudtoken vulnerabilities

Vulert verdict on cloudtoken 2.1.18 i

Updated on 22 Oct 2026

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

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

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

  • Current release 2.1.18 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 9 packages i
  • Last release 28 months ago 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 cloudtoken, 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
2.1.18 31 May 2024 none — — Details →
2.1.17 01 May 2024 none — — Details →
2.1.16 08 Apr 2024 none — — Details →
2.1.15 03 Apr 2024 none — — Details →
2.1.14 19 Mar 2024 none — — Details →
2.1.13 04 Jan 2024 none — — Details →
2.1.12 19 Dec 2023 none — — Details →
2.1.11 09 Nov 2023 none — — Details →
2.1.10 23 Aug 2023 none — — Details →
2.1.9 25 Jul 2023 none — — Details →
2.1.8 02 Jun 2023 none — — Details →
2.1.7 29 May 2023 none — — Details →
2.1.6 19 May 2023 none — — Details →
2.1.2 23 Nov 2022 none — — Details →
2.1.1 27 Jul 2022 none — — Details →
2.1.0 12 May 2022 none — — Details →
2.0.10 16 Mar 2022 none — — Details →
2.0.9 01 Sep 2021 none — — Details →
2.0.8 18 Jul 2021 none — — Details →
2.0.7 26 May 2021 none — — Details →
2.0.6 25 May 2021 none — — Details →
2.0.5 03 May 2021 none — — Details →
2.0.4 30 Apr 2021 none — — Details →
2.0.3 29 Apr 2021 none — — Details →
2.0.2 28 Apr 2021 none — — Details →
2.0.1 27 Apr 2021 none — — Details →
2.0.0 27 Apr 2021 none — — Details →
0.1.764 10 Dec 2020 none non-standard — Details →
0.1.761 07 Dec 2020 none non-standard — Details →
0.1.754 02 Dec 2020 none non-standard — Details →
0.1.731 09 Nov 2020 none non-standard — Details →
0.1.707 28 Oct 2020 none non-standard — Details →
0.1.685 06 Oct 2020 none non-standard — Details →
0.1.684 06 Oct 2020 none non-standard — Details →
0.1.255 04 Aug 2019 none non-standard — Details →
0.1.123 26 Mar 2019 none non-standard — Details →
0.1.122 26 Mar 2019 none non-standard — Details →
0.1.84 17 Feb 2019 none non-standard — Details →
0.1.73 08 Feb 2019 none non-standard — Details →
0.1.71 07 Feb 2019 none non-standard — Details →
0.1.59 28 Jan 2019 none non-standard — Details →
0.1.54 08 Jan 2019 none non-standard — Details →
0.1.53 08 Jan 2019 none non-standard — Details →
0.1.52 27 Dec 2018 none non-standard — Details →
0.1.51 18 Dec 2018 none non-standard — Details →
0.1.50 18 Dec 2018 none non-standard — Details →
0.1.49 11 Oct 2018 none non-standard — Details →
0.1.48 18 Sep 2018 none non-standard — Details →
0.1.47 18 Sep 2018 none non-standard — Details →
0.1.46 18 Sep 2018 none non-standard — Details →
0.1.45 18 Sep 2018 none non-standard — Details →
0.1.44 17 Sep 2018 none non-standard — Details →
0.1.43 21 Aug 2018 none non-standard — Details →
0.1.24 09 Aug 2018 none non-standard — Details →
0.1.23 06 Aug 2018 L1 U1 non-standard Yes Details →
0.1.22 01 Aug 2018 L1 U1 non-standard Yes Details →
0.1.21 24 Jul 2018 L1 U1 non-standard Yes Details →
0.1.19 20 May 2018 L1 U1 non-standard Yes Details →
0.1.18 22 Apr 2018 L1 U1 non-standard Yes Details →
0.1.17 20 Apr 2018 L1 U1 non-standard Yes Details →
0.1.16 20 Apr 2018 L1 U1 non-standard Yes Details →
0.1.15 04 Apr 2018 L1 U1 non-standard Yes Details →
0.1.14 04 Apr 2018 L1 U1 non-standard Yes Details →
0.1.13 05 Mar 2018 L1 U1 non-standard Yes Details →
0.1.12 11 Feb 2018 L1 U1 non-standard Yes Details →
0.1.11 17 Jan 2018 L1 U1 non-standard Yes Details →
0.1.10 19 Dec 2017 L1 U1 non-standard Yes Details →
0.1.9 12 Dec 2017 L1 U1 non-standard Yes Details →
0.1.8 11 Dec 2017 L1 U1 non-standard Yes Details →
0.1.7 29 Nov 2017 L1 U1 non-standard Yes Details →
0.1.6 29 Nov 2017 L1 U1 non-standard Yes Details →
0.1.5 28 Nov 2017 L1 U1 non-standard Yes Details →
0.1.3 26 Nov 2017 L1 U1 non-standard Yes Details →
0.1.2 24 Nov 2017 L1 U1 non-standard Yes Details →
0.1.1 24 Nov 2017 L1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 1

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 cloudtoken

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-13390: Cloudtoken Insufficiently Protects Credentials 6.1 low 0.1.24 13 May 2022
CVE-2018-13390: Unauthenticated Access to cloudtoken Daemon on Linux N/A unrated 0.1.24 10 Aug 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 cloudtoken

Is cloudtoken safe to use?

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

Vulert scores cloudtoken 66/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 cloudtoken affected?

No. 2.1.18, 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 cloudtoken should I use?

2.1.18 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 cloudtoken have?

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

0 vulnerabilities were recorded for cloudtoken in the last 12 months, and the oldest entry in this database dates to 10 Aug 2018. 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 cloudtoken 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 cloudtoken for upcoming vulnerabilities?

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