CVE-2020-4059: In mversion before 2.0.0, there is a command injection vulnerability

Q: How do I fix CVE-2020-4059?

mversion: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-4059 being exploited?

CVE-2020-4059 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-2020-4059 affect?

CVE-2020-4059 affects mversion. Severity is high (CVSS 7.3). In mversion before 2.0.0, there is a command injection vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This vulnerability is patched by version 2.0.0.

Q: How urgent is CVE-2020-4059?

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

This month

HIGH 7.3REMOTEUPGRADE

CVE-2020-4059 is a high-severity flaw (CVSS 7.3) affecting mversion. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In mversion before 2.0.0, there is a command injection vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This vulnerability is patched by version 2.0.0. Previous releases are deprecated in npm. As a workaround, make sure to escape git commit messages when using the commitMessage option for the update function.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.6% (top 15%)
CISA exploited list	No
Weakness	CWE-77
Published	2020-06-18
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: mversion project

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

Am I affected?

Timeline

2020-06-18 20:15 UTCPublished CVE record published
2026-06-17 03:19 UTCUpdated Record last modified

mversion project mversion UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mversion

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-2020-4059?

mversion: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2020-4059 being exploited?

CVE-2020-4059 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-2020-4059 affect?

CVE-2020-4059 affects mversion. Severity is high (CVSS 7.3). In mversion before 2.0.0, there is a command injection vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This vulnerability is patched by version 2.0.0.

How urgent is CVE-2020-4059?

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

Software pages

Git vulnerabilities

Related CVEs

CVE-2020-7688 HIGH 8.4 UPGRADE The issue occurs because tagName user input is formatted inside the exec function is executed without any chec

References

← Back to latest CVEs