Vulnerability Database · Go · github.com/Masterminds/vcs · Version

github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc

v0.0.0-20161011150022-cff893e7f9fc is affected by 3 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v1.13.3.

Critical 1 High 0 Medium 0 Low 0 Unrated 2

Released 11 Oct 2016 Licence MIT Also known from other sources 2 Newer releases 250 Database updated 23/Oct/2026

Release and licence data published by the Go module proxy. 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 Vulnerabilities affecting this version

github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc vulnerabilities

3 vulnerabilities cover github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2022-21235: Command Injection Vulnerability with Mercurial in VCS 9.8 critical 1.13.2 01 Apr 2022
CVE-2022-21235: Command Injection Vulnerability with Mercurial in VCS N/A unrated 1.13.3 01 Jul 2022
CVE-2022-21235: Command Injection in github.com/Masterminds/vcs N/A unrated 1.13.3 01 Jul 2022

Looking for another version, or everything Vulert holds for github.com/Masterminds/vcs?

All versions → Full vulnerability list →

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 github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc

Is github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover github.com/Masterminds/vcs v0.0.0-20161011150022-cff893e7f9fc: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is v1.13.3, and each entry above names the fixed version to move to.

Which version of github.com/Masterminds/vcs should I use instead of v0.0.0-20161011150022-cff893e7f9fc?

v1.13.3 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is v0.0.0-20161011150022-cff893e7f9fc the latest release of github.com/Masterminds/vcs?

No. v0.0.0-20161011150022-cff893e7f9fc was published 11 Oct 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor github.com/Masterminds/vcs for upcoming vulnerabilities?

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