Incorrect Default Permissions The advisory has been revoked - it doesn't affect any version of package vagrant (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Default Permissions vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-RUBY-VAGRANT-10590746
- published4 Jul 2025
- disclosed2 Jul 2025
- creditbcoles
Introduced: 2 Jul 2025
NewCVE-2025-34075 (opens in a new tab)How to fix?
Upgrade vagrant to version 2.4.7 or higher.
Amendment
This was deemed not a vulnerability.
Overview
Affected versions of this package are vulnerable to Incorrect Default Permissions via the 'Vagrantfile' configuration file. An attacker can execute arbitrary code on the host system by appending malicious Ruby code to the shared configuration file from within the guest virtual machine, which is then executed with the host user's privileges when any command is run.
Note:
This is only exploitable if the attacker has shell access to the guest VM and the default synced folder configuration is used. By default the host system is mounted into guest VM under /vagrant (or C:\vagrant on Windows).