VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/Masterminds/vcs: vulnerability history, versions and safety

github.com/Masterminds/vcs is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Apr 2022 to Jul 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 U2
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 github.com/Masterminds/vcs vulnerabilities

Vulert verdict on github.com/Masterminds/vcs v1.13.3 i

Updated on 23 Oct 2026

Action needed: v1.13.3 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 56/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.13.3 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 01 Jul 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 205 i
  • OpenSSF scorecard 3/10 i
  • Last release 54 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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 github.com/Masterminds/vcs, 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
v0.0.0-20260430163323-2a0cab971a02 30 Apr 2026 C1 U2 MIT Yes Details →
v1.13.4-0.20260430163323-2a0cab971a02 30 Apr 2026 C1 U2 MIT Yes Details →
v1.13.4-0.20251204144000-e691f44a376b 04 Dec 2025 C1 U2 MIT Yes Details →
v1.13.3 31 Mar 2022 C1 U2 MIT Yes Details →
v1.13.3-0.20220331143225-7d3c35890170 31 Mar 2022 C1 U2 MIT Yes Details →
v1.13.3-0.20220331142750-c11ae94a68b9 31 Mar 2022 C1 U2 MIT Yes Details →
v0.0.0-20190709221538-f94282d8632a 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190709213122-90addbc0a818 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190709212550-14a09063c6cf 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190709210324-4d6970958bbc 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190709183935-461cd35ff2a2 09 Jul 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190613193048-8bf0f9b658d6 13 Jun 2019 C1 U2 MIT Yes Details →
v1.13.1-0.20190613185108-5b2733df61ad 13 Jun 2019 C1 U2 MIT Yes Details →
v0.0.0-20190227142811-b4f55832432b 27 Feb 2019 C1 U2 MIT Yes Details →
v1.13.0 27 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190227141534-21790f0f7b30 27 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190227011125-f9b4851ac280 27 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190226213322-9b56ef1fddc6 26 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190225210845-ecf366d52cd4 25 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190208233656-2f0344fbfdc7 08 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20190208210831-56e31f59151a 08 Feb 2019 C1 U2 MIT Yes Details →
v1.12.1-0.20180819012407-0afcb7510f90 19 Aug 2018 C1 U2 MIT Yes Details →
v0.0.0-20180403014055-df81cd881f84 03 Apr 2018 C1 U2 MIT Yes Details →
v1.12.1-0.20180403014055-df81cd881f84 03 Apr 2018 C1 U2 MIT Yes Details →
v1.12.1-0.20180305235349-4dafb2dc6205 05 Mar 2018 C1 U2 MIT Yes Details →
v1.12.1-0.20180305235343-dfb47aeef3e0 05 Mar 2018 C1 U2 MIT Yes Details →
v0.0.0-20170911144531-6f1c6d150500 11 Sep 2017 C1 U2 MIT Yes Details →
v1.12.0 11 Sep 2017 C1 U2 MIT Yes Details →
v1.11.2-0.20170911143710-ea945b4662ba 11 Sep 2017 C1 U2 MIT Yes Details →
v1.11.2-0.20170911142558-98687a3065b1 11 Sep 2017 C1 U2 MIT Yes Details →
v1.11.2-0.20170911140403-eabae39a6d53 11 Sep 2017 C1 U2 MIT Yes Details →
v1.11.2-0.20170908172405-d5c02827c217 08 Sep 2017 C1 U2 MIT Yes Details →
v1.11.2-0.20170716014021-d8a343481a4d 16 Jul 2017 C1 U2 MIT Yes Details →
v0.0.0-20170428132344-3084677c2c18 28 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1 28 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170428130348-6594752281f2 28 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170424144733-92b575841817 24 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170423162439-00af9df2743f 23 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170423162205-c332ca6326e8 23 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170421223030-65b8bab27f7b 21 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418203546-500831de79f5 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418203432-085dbd45669c 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418195759-0302f471f326 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418195648-3df2830cf163 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418194816-cee519f2f401 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418194350-9e54342be425 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418172357-68f7396b6d6f 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418153740-92453b58636b 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418152953-982e2f49cb11 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.1-0.20170418122316-93ea79b60a7a 18 Apr 2017 C1 U2 MIT Yes Details →
v1.11.0 24 Mar 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170324015123-852adcd2f6d6 24 Mar 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170323010514-adebf36aa3f0 23 Mar 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170323010008-bac9f210a7ab 23 Mar 2017 C1 U2 MIT Yes Details →
v0.0.0-20170130142604-abd1ea7037d3 30 Jan 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170130142604-abd1ea7037d3 30 Jan 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170129154621-579b018de295 29 Jan 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170125144143-2573480d48df 25 Jan 2017 C1 U2 MIT Yes Details →
v1.10.3-0.20170124183507-04a2a982ed43 24 Jan 2017 C1 U2 MIT Yes Details →
v1.10.2 24 Jan 2017 C1 U2 MIT Yes Details →
v1.10.2-0.20170124143818-4ae26b8f9c18 24 Jan 2017 C1 U2 MIT Yes Details →
v1.10.2-0.20170124143141-504bd82e1daa 24 Jan 2017 C1 U2 MIT Yes Details →
v1.10.2-0.20170121005340-2449b6d05bf2 21 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1 18 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1-0.20170117164111-a76894c51cb3 17 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1-0.20170117163501-0d1e1f8f28bd 17 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1-0.20170113220855-48f4652acbb6 13 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1-0.20170113220703-1e1db8bf38cd 13 Jan 2017 C1 U2 MIT Yes Details →
v1.10.1-0.20170111142745-9a6e212fd558 11 Jan 2017 C1 U2 MIT Yes Details →
v1.10.0 09 Jan 2017 C1 U2 MIT Yes Details →
v1.9.1-0.20170106143119-83dde1960cd1 06 Jan 2017 C1 U2 MIT Yes Details →
v1.9.1-0.20170105160850-95aab3c06a57 05 Jan 2017 C1 U2 MIT Yes Details →
v1.9.1-0.20170104160130-6abbba97132d 04 Jan 2017 C1 U2 MIT Yes Details →
v1.9.1-0.20161229155934-f0e30a85e28e 29 Dec 2016 C1 U2 MIT Yes Details →
v1.9.1-0.20161204150000-3c78e163d609 04 Dec 2016 C1 U2 MIT Yes Details →
v1.9.1-0.20161204145837-8e5ea52f387e 04 Dec 2016 C1 U2 MIT Yes Details →
v1.9.1-0.20161204052032-05ae2555ff6a 04 Dec 2016 C1 U2 MIT Yes Details →
v1.9.1-0.20161204051425-cec96d1779a7 04 Dec 2016 C1 U2 MIT Yes Details →
v0.0.0-20161118141247-ccb44ce72b68 18 Nov 2016 C1 U2 MIT Yes Details →
v1.9.0 18 Nov 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161118141137-5154f23ec4fb 18 Nov 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161116175747-d27723cff2b8 16 Nov 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161116154314-7efd3cf27c80 16 Nov 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161115162547-cb77a17c0403 15 Nov 2016 C1 U2 MIT Yes Details →
v0.0.0-20161011150022-cff893e7f9fc 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011150022-cff893e7f9fc 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011145721-e92d56536cb5 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011144349-09bcdb2df413 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011144349-eabeaa9c453b 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011144328-bbe6f5bf4c9a 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011142511-a623ad7c1cf0 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161011140642-9ec89844578c 11 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161007234541-383a73934ed0 07 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161007233936-fe47cc13ac42 07 Oct 2016 C1 U2 MIT Yes Details →
v1.8.1-0.20161007233820-75262ba84966 07 Oct 2016 C1 U2 MIT Yes Details →
v0.0.0-20160629141518-fbe9fb6ad5b5 29 Jun 2016 C1 U2 MIT Yes Details →
v1.8.0 29 Jun 2016 C1 U2 MIT Yes Details →
v0.0.0-20160629131050-72daa9d7d9ba 29 Jun 2016 C1 U2 MIT Yes Details →
v0.0.0-20160629131039-c8d6b8a21cc9 29 Jun 2016 C1 U2 MIT Yes Details →
v0.0.0-20160629131031-d7a05f09e40e 29 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160628194648-f816fcc3bff7 28 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160628170404-d1f176f332cd 28 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160628164218-93a9b9e23e7d 28 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160624155943-4de1ea1914c3 24 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160624155204-fd38593a4d21 24 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160621164737-7a55b7a7307c 21 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160621154759-acc61d838091 21 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160621151457-ed2e72488450 21 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160620133150-539806f53135 20 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160610130233-614717afb239 10 Jun 2016 C1 U2 — Yes Details →
v0.0.0-20160505133249-7af28b64c5ec 05 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504194847-bd01f190768f 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504194838-12cfd8495012 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504143054-b21f3eb07530 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504142052-87e45883225e 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504141550-7fc9197fb54b 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504140326-ab99de82003d 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160504140100-db40b9f2b26e 04 May 2016 C1 U2 — Yes Details →
v0.0.0-20160503191723-63b0b91373d9 03 May 2016 C1 U2 — Yes Details →

The newest 120 of 250 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/Masterminds/vcs

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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

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 github.com/Masterminds/vcs

Is github.com/Masterminds/vcs safe to use?

Vulert records 3 vulnerabilities for github.com/Masterminds/vcs in Go: 1 critical, 0 high, 0 medium and 0 low, plus 2 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 github.com/Masterminds/vcs's Vulert package health score?

Vulert scores github.com/Masterminds/vcs 56/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 github.com/Masterminds/vcs affected?

Yes. v1.13.3, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/Masterminds/vcs should I use?

v1.13.3 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 github.com/Masterminds/vcs have?

3 vulnerabilities are recorded for github.com/Masterminds/vcs in the Go ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 2 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 github.com/Masterminds/vcs vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/Masterminds/vcs in the last 12 months, and the oldest entry in this database dates to 01 Apr 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 github.com/Masterminds/vcs 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 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.