# CVE-2025-34075: HashiCorp Vagrant has code injection vulnerability through default synced folders


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** GHSA-hqp6-mjw3-f586

## What is CVE-2025-34075?

CVE-2025-34075 is a vulnerability in vagrant, published on 2 Jul 2025. 

### Official description

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Initially assigned to document an issues that allows guest VM to modify the host’s Vagrantfile via default synced folder, leading to host-side code execution. Rejected as CVE due to documented, intended behavior that does not violate a claimed security boundary.  https://developer.hashicorp.com/vagrant/docs/synced-folders

## Which versions are affected by CVE-2025-34075?

2 open source packages ship an affected version, including vagrant.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vagrant` | RubyGems | From 2.2.10 | 2.4.7 |
| `vagrant` | RubyGems | From 2.2.10 | 2.4.7 |

## How do I fix CVE-2025-34075?

Upgrade vagrant to 2.4.7 or later.

## Is CVE-2025-34075 being exploited?

There is no known exploitation of CVE-2025-34075 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34075 and fix it if it is affected.

What it is: CVE-2025-34075 is a vulnerability in vagrant, published on 2 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-34075 in the wild and no public exploit code.

Affected packages and fixed versions:
- vagrant (RubyGems): affected from 2.2.10; fixed in 2.4.7
- vagrant (RubyGems): affected from 2.2.10; fixed in 2.4.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34075/ (Markdown: https://insights.sbomify.com/CVE-2025-34075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34075
- OSV: https://osv.dev/vulnerability/CVE-2025-34075

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34075/
Summaries are generated and may contain mistakes; the official description above is the record.