CVE-2022-21235: The package github.com/masterminds/vcs before 1.13.3 are vulnerable to Command Injection via argument injectio

Q: How do I fix CVE-2022-21235?

vcs: upgrade to 1.1.13. Exact commands for each OS are on this page.

Q: Is CVE-2022-21235 being exploited?

CVE-2022-21235 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-21235 affect?

CVE-2022-21235 affects vcs. Severity is high (CVSS 8.1). The package github.com/masterminds/vcs before 1.13.3 are vulnerable to Command Injection via argument injection. When hg is executed, argument strings are passed to hg in a way that additional flags can be set. The additional flags can be u

Q: How urgent is CVE-2022-21235?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2022-21235 is a high-severity flaw (CVSS 8.1) affecting vcs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The package github.com/masterminds/vcs before 1.13.3 are vulnerable to Command Injection via argument injection. When hg is executed, argument strings are passed to hg in a way that additional flags can be set. The additional flags can be used to perform a command injection.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-88
Published	2022-04-01
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: vcs project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-04-01 16:15 UTCPublished CVE record published
2026-06-17 04:25 UTCUpdated Record last modified

vcs project vcs UPGRADE

Affected: < 1.1.13

Fixed in: 1.1.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vcs || rpm -q vcs || vcs --version

2. UPGRADE to 1.1.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vcs

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vcs

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-21235?

vcs: upgrade to 1.1.13. Exact commands for each OS are on this page.

Is CVE-2022-21235 being exploited?

CVE-2022-21235 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-21235 affect?

CVE-2022-21235 affects vcs. Severity is high (CVSS 8.1). The package github.com/masterminds/vcs before 1.13.3 are vulnerable to Command Injection via argument injection. When hg is executed, argument strings are passed to hg in a way that additional flags can be set. The additional flags can be u

How urgent is CVE-2022-21235?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

References

← Back to latest CVEs