CVE-2021-21361: The `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to

This month

MEDIUM 5.3UPGRADE

CVE-2021-21361 is a medium-severity flaw (CVSS 5.3) affecting vagrant. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables. When this Gradle plugin is executed in public CI/CD, this can lead to sensitive credentials being exposed to malicious actors. This is fixed in version 3.0.0.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Physical
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Weakness	CWE-532
Published	2021-03-09
Last modified	2026-06-17

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

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

Am I affected?

Timeline

2021-03-09 01:15 UTCPublished CVE record published
2026-06-17 03:35 UTCUpdated Record last modified

vagrant project vagrant UPGRADE

Affected: < 0.6 · >= 2.0 and < 3.0.0

Fixed in: 0.6, 3.0.0

Safe to downgrade to: a release before 2.0

1. Check installed version

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

2. UPGRADE to 0.6 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vagrant

Note

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

3. If no update is available yet, DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison vagrant sudo apt install vagrant=<VERSION_BEFORE_2.0> sudo apt-mark hold vagrant

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vagrant sudo dnf downgrade vagrant-<VERSION_BEFORE_2.0> 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.

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-2021-21361?

vagrant: upgrade to 0.6, 3.0.0. Exact commands for each OS are on this page.

Is CVE-2021-21361 being exploited?

CVE-2021-21361 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-2021-21361 affect?

CVE-2021-21361 affects vagrant. Severity is medium (CVSS 5.3). The `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables. When this Gradle plugin is executed in public CI/CD, this can lead to sensitive

How urgent is CVE-2021-21361?

Priority 40/100. Public exploit reference

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-2017-16777 HIGH 7.8 DOWNGRADE If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is
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