CVE-2023-5834: HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junct

Q: How do I fix CVE-2023-5834?

vagrant: upgrade to 2.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-5834 being exploited?

CVE-2023-5834 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-2023-5834 affect?

CVE-2023-5834 affects vagrant. Severity is low (CVSS 3.8). HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.

Q: How urgent is CVE-2023-5834?

Priority 17/100. No elevated risk signals yet.

Routine

LOW 3.8UPGRADE

CVE-2023-5834 is a low-severity flaw (CVSS 3.8) affecting vagrant. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.8 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 85%)
CISA exploited list	No
Weakness	CWE-1386, CWE-59
Published	2023-10-27
Last modified	2026-06-17

Publisher (CNA): HashiCorp Inc. · Vendor: hashicorp

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

Am I affected?

Timeline

2023-10-27 22:15 UTCPublished CVE record published
2026-06-17 06:49 UTCUpdated Record last modified

hashicorp vagrant UPGRADE

Affected: < 2.4.0

Fixed in: 2.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.4.0 (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.

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-2023-5834?

vagrant: upgrade to 2.4.0. Exact commands for each OS are on this page.

Is CVE-2023-5834 being exploited?

CVE-2023-5834 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-2023-5834 affect?

CVE-2023-5834 affects vagrant. Severity is low (CVSS 3.8). HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.

How urgent is CVE-2023-5834?

Priority 17/100. No elevated risk signals yet.

Software pages

Windows vulnerabilities

Related CVEs

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