CVE-2017-16777: If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is

This month

HIGH 7.8DOWNGRADE

CVE-2017-16777 is a high-severity flaw (CVSS 7.8) affecting vagrant. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is not, a local attacker can create a fake application directory and exploit the suid sudo helper in order to escalate to root.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-427
Published	2017-11-16
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: hashicorp

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

Am I affected?

Timeline

2017-11-16 15:29 UTCPublished CVE record published
2026-06-17 01:09 UTCUpdated Record last modified

hashicorp vagrant DOWNGRADE

Affected: 5.0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0.3

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 5.0.3 (Debian / Ubuntu)

apt-cache madison vagrant sudo apt install vagrant=<VERSION_BEFORE_5.0.3> sudo apt-mark hold vagrant

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vagrant sudo dnf downgrade vagrant-<VERSION_BEFORE_5.0.3> sudo dnf versionlock add vagrant

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Hashicorp vagrant-vmware-fusion 5.0.3 - Local Privilege Escalation

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-2017-16777?

vagrant: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-16777 being exploited?

CVE-2017-16777 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-2017-16777 affect?

CVE-2017-16777 affects vagrant. Severity is high (CVSS 7.8). If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is not, a local attacker can create a fake application directory and exploit the suid sudo helper in order to escalate to root.

How urgent is CVE-2017-16777?

Priority 48/100. High severity; Public exploit reference

Software pages

VMware vulnerabilities · Sudo vulnerabilities

Related CVEs

CVE-2023-5834 LOW 3.8 UPGRADE HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junct
CVE-2022-42717 HIGH 7.8 UPGRADE An issue was discovered in Hashicorp Packer before 2.3.1
CVE-2021-21361 MEDIUM 5.3 UPGRADE The `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to
CVE-2017-16001 HIGH 7.8 DOWNGRADE In HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.1, a local attacker or malware can s

References

← Back to latest CVEs