CVE-2022-21187: The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection

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

libvcs: upgrade to 0.11.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-21187 being exploited?

CVE-2022-21187 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-21187 affect?

CVE-2022-21187 affects libvcs. Severity is high (CVSS 8.1). The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was pos

Q: How urgent is CVE-2022-21187?

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

This month

HIGH 8.1REMOTEUPGRADE

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

The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was possible to get arbitrary command execution.

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	3.6% (top 10%)
CISA exploited list	No
Weakness	CWE-88
Published	2022-03-14
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: libvcs project

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

Am I affected?

Timeline

2022-03-14 18:15 UTCPublished CVE record published
2026-06-17 04:25 UTCUpdated Record last modified

libvcs project libvcs UPGRADE

Affected: < 0.11.1

Fixed in: 0.11.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 0.11.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libvcs

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-21187?

libvcs: upgrade to 0.11.1. Exact commands for each OS are on this page.

Is CVE-2022-21187 being exploited?

CVE-2022-21187 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-21187 affect?

CVE-2022-21187 affects libvcs. Severity is high (CVSS 8.1). The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was pos

How urgent is CVE-2022-21187?

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

References

← Back to latest CVEs