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.
Loading...
Loading...
This low-severity CVE scores 3.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
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.
October 27, 2023
June 17, 2026
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/hashicorp/vagrant | — | 2.4.0 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-5834
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.