VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

libvcs: vulnerability history, versions and safety

libvcs is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 0 release, first recorded in Mar 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 C1 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 libvcs vulnerabilities

Vulert verdict on libvcs 0.46.0 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.46.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 15 Mar 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 58 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT 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 libvcs, 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
0.46.0 30 Aug 2026 none MIT — Details →
0.45.1 11 Jul 2026 none MIT — Details →
0.45.0 28 Jun 2026 none MIT — Details →
0.44.0 21 Jun 2026 none MIT — Details →
0.43.0 20 Jun 2026 none MIT — Details →
0.42.0 31 May 2026 none MIT — Details →
0.41.0 10 May 2026 none MIT — Details →
0.40.0 25 Apr 2026 none MIT — Details →
0.39.0 07 Feb 2026 none MIT — Details →
0.38.6 27 Jan 2026 none MIT — Details →
0.38.5 25 Jan 2026 none MIT — Details →
0.38.4 25 Jan 2026 none MIT — Details →
0.38.3 25 Jan 2026 none MIT — Details →
0.38.2 24 Jan 2026 none MIT — Details →
0.38.1 06 Dec 2025 none MIT — Details →
0.38.0 30 Nov 2025 none MIT — Details →
0.38.0a0 30 Nov 2025 none MIT — Details →
0.37.0 01 Nov 2025 none MIT — Details →
0.36.0 22 Jun 2025 none MIT — Details →
0.35.1 21 Jun 2025 none MIT — Details →
0.35.0 22 Feb 2025 none MIT — Details →
0.34.0 22 Nov 2024 none MIT — Details →
0.33.0 13 Oct 2024 none MIT — Details →
0.32.3 13 Oct 2024 none MIT — Details →
0.32.2 13 Oct 2024 none MIT — Details →
0.32.1 12 Oct 2024 none MIT — Details →
0.32.0 12 Oct 2024 none MIT — Details →
0.31.0 12 Oct 2024 none MIT — Details →
0.30.1 18 Jun 2024 none MIT — Details →
0.30.0 18 Jun 2024 none MIT — Details →
0.29.0 24 Mar 2024 none MIT — Details →
0.28.2 17 Feb 2024 none MIT — Details →
0.28.1 08 Feb 2024 none MIT — Details →
0.28.0 07 Feb 2024 none MIT — Details →
0.27.0 06 Feb 2024 none MIT — Details →
0.26.0 26 Nov 2023 none MIT — Details →
0.25.1 23 Nov 2023 none MIT — Details →
0.25.0 19 Nov 2023 none MIT — Details →
0.24.0 22 Oct 2023 none MIT — Details →
0.23.0.post0 20 Aug 2023 none MIT — Details →
0.23.0 20 Aug 2023 none MIT — Details →
0.22.2 20 Aug 2023 none MIT — Details →
0.22.1 28 May 2023 none MIT — Details →
0.22.0 27 May 2023 none MIT — Details →
0.21.2 07 Apr 2023 none MIT — Details →
0.21.1 15 Mar 2023 none MIT — Details →
0.21.0 15 Mar 2023 none MIT — Details →
0.20.0 01 Nov 2022 none MIT — Details →
0.19.1 23 Oct 2022 none MIT — Details →
0.19.0 23 Oct 2022 none MIT — Details →
0.19.0a0 23 Oct 2022 none MIT — Details →
0.18.1 23 Oct 2022 none MIT — Details →
0.18.0 10 Oct 2022 none MIT — Details →
0.17.0 26 Sep 2022 none MIT — Details →
0.17.0a1 26 Sep 2022 none MIT — Details →
0.17.0a0 25 Sep 2022 none MIT — Details →
0.13.7 24 Sep 2022 none MIT — Details →
0.16.5 22 Sep 2022 none MIT — Details →
0.16.4 18 Sep 2022 none MIT — Details →
0.16.4a0 18 Sep 2022 none MIT — Details →
0.16.3 18 Sep 2022 none MIT — Details →
0.16.3a0 18 Sep 2022 none MIT — Details →
0.16.2 12 Sep 2022 none MIT — Details →
0.16.1 11 Sep 2022 none MIT — Details →
0.16.0 11 Sep 2022 none MIT — Details →
0.15.0 11 Sep 2022 none MIT — Details →
0.15.0a3 11 Sep 2022 none MIT — Details →
0.15.0a2 11 Sep 2022 none MIT — Details →
0.15.0a1 06 Sep 2022 none MIT — Details →
0.15.0a0 28 Aug 2022 none MIT — Details →
0.14.0 31 Jul 2022 none MIT — Details →
0.14.0a8 31 Jul 2022 none MIT — Details →
0.14.0a7 30 Jul 2022 none MIT — Details →
0.14.0a6 10 Jul 2022 none MIT — Details →
0.14.0a5 10 Jul 2022 none MIT — Details →
0.14.0a4 09 Jul 2022 none MIT — Details →
0.14.0a3 09 Jul 2022 none MIT — Details →
0.14.0a2 25 Jun 2022 none MIT — Details →
0.14.0a1 23 Jun 2022 none MIT — Details →
0.14.0a0 21 Jun 2022 none MIT — Details →
0.13.6 19 Jun 2022 none MIT — Details →
0.13.5 18 Jun 2022 none MIT — Details →
0.13.4 18 Jun 2022 none MIT — Details →
0.13.3 18 Jun 2022 none MIT — Details →
0.13.2 12 Jun 2022 none MIT — Details →
0.13.1 02 Jun 2022 none MIT — Details →
0.13.0 31 May 2022 none MIT — Details →
0.13.0a18 30 May 2022 none MIT — Details →
0.13.0a17 30 May 2022 none MIT — Details →
0.12.4 30 May 2022 none MIT — Details →
0.13.0a16 30 May 2022 none MIT — Details →
0.13.0a15 30 May 2022 none MIT — Details →
0.13.0a14 30 May 2022 none MIT — Details →
0.13.0a13 29 May 2022 none MIT — Details →
0.13.0a12 29 May 2022 none MIT — Details →
0.12.3 28 May 2022 none MIT — Details →
0.13.0a11 28 May 2022 none MIT — Details →
0.13.0a10 22 May 2022 none MIT — Details →
0.13.0a9 15 May 2022 none MIT — Details →
0.13.0a8 15 May 2022 none MIT — Details →
0.13.0a7 14 May 2022 none — — Details →
0.13.0a5 10 May 2022 none — — Details →
0.12.2 10 May 2022 none — — Details →
0.13.0a4 10 May 2022 none — — Details →
0.12.1 10 May 2022 none — — Details →
0.13.0a3 08 May 2022 none — — Details →
0.13.0a2 08 May 2022 none — — Details →
0.13.0a1 08 May 2022 none — — Details →
0.13.0a0 01 May 2022 none — — Details →
0.12.0 24 Apr 2022 none — — Details →
0.12.0b35 24 Apr 2022 none — — Details →
0.12.0b34 23 Apr 2022 none — — Details →
0.12.0b33 23 Apr 2022 none — — Details →
0.12.0b32 21 Apr 2022 none — — Details →
0.12.0b31 16 Apr 2022 none — — Details →
0.12.0b30 16 Apr 2022 none — — Details →
0.12.0b29 14 Apr 2022 none — — Details →
0.12.0b28 14 Apr 2022 none — — Details →
0.12.0b27 13 Apr 2022 none — — Details →
0.12.0b26 12 Apr 2022 none — — Details →

The newest 120 of 176 versions Vulert tracks. 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 libvcs

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-21187: Command Injection in libvcs and vcspull 8.1 critical 0.11.1 15 Mar 2022
CVE-2022-21187: Command Injection in libvcs Package N/A unrated 0.11.1 14 Mar 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 libvcs

Is libvcs safe to use?

Vulert records 2 vulnerabilities for libvcs in PyPI: 1 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 libvcs's Vulert package health score?

Vulert scores libvcs 70/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 libvcs affected?

No. 0.46.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 libvcs should I use?

0.46.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 libvcs have?

2 vulnerabilities are recorded for libvcs in the PyPI ecosystem: 1 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 libvcs vulnerabilities disclosed?

0 vulnerabilities were recorded for libvcs in the last 12 months, and the oldest entry in this database dates to 14 Mar 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 libvcs 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 libvcs for upcoming vulnerabilities?

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