# HashiCorp Vagrant has code injection vulnerability through default synced folders

Advisory record · `GHSA-hqp6-mjw3-f586`

- **Identifiers:** `GHSA-hqp6-mjw3-f586` · `CVE-2025-34075`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) · [CWE-276](https://cwe.mitre.org/data/definitions/276.html) · [CWE-668](https://cwe.mitre.org/data/definitions/668.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 2 Jul 2025
- **Updated:** 5 Jul 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Jul 2025, 21:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vagrant` (RubyGems): affected `>=2.2.10, <2.4.7`; fixed in `2.4.7`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 2 Jul 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-hqp6-mjw3-f586](https://github.com/advisories/GHSA-hqp6-mjw3-f586)
- [OSV: GHSA-hqp6-mjw3-f586](https://osv.dev/vulnerability/GHSA-hqp6-mjw3-f586)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-34075>
- <https://github.com/hashicorp/vagrant/issues/13688>
- <https://github.com/hashicorp/vagrant/commit/abe87b2fdc124ef426c016d44d2f6f4792f0cbe3>
- <https://developer.hashicorp.com/vagrant>
- <https://developer.hashicorp.com/vagrant/docs/synced-folders/basic_usage>
- <https://developer.hashicorp.com/vagrant/docs/vagrantfile>
- <https://github.com/advisories/GHSA-hqp6-mjw3-f586>
- <https://github.com/hashicorp/vagrant>
- <https://github.com/rubysec/ruby-advisory-db/blob/master/gems/vagrant/CVE-2025-34075.yml>
- <https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/local/vagrant_synced_folder_vagrantfile_breakout.rb>
- <https://vulncheck.com/advisories/hashicorp-vagrant-synced-folder-vagrantfile-breakout>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hqp6-mjw3-f586>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hqp6-mjw3-f586/>. Everything for agents: <https://agentprime.io/llms.txt>.