{"answers":{"affected":"2 open source packages ship an affected version, including vagrant.","exploited":"There is no known exploitation of CVE-2025-34075 in the wild and no public exploit code.","fix":"Upgrade vagrant to 2.4.7 or later.","what":"CVE-2025-34075 is a vulnerability in vagrant, published on 2 Jul 2025."},"fix_prompt":"Check this codebase for CVE-2025-34075 and fix it if it is affected.\n\nWhat it is: CVE-2025-34075 is a vulnerability in vagrant, published on 2 Jul 2025. \nExploitation: There is no known exploitation of CVE-2025-34075 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vagrant (RubyGems): affected from 2.2.10; fixed in 2.4.7\n- vagrant (RubyGems): affected from 2.2.10; fixed in 2.4.7\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-34075/ (Markdown: https://insights.sbomify.com/CVE-2025-34075/index.md)","id":"CVE-2025-34075","markdown":"https://insights.sbomify.com/CVE-2025-34075/index.md","name":"CVE-2025-34075","record":{"aliases":["GHSA-hqp6-mjw3-f586"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\n\nInitially 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","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HashiCorp Vagrant has code injection vulnerability through default synced folders","id":"CVE-2025-34075","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":null,"year":"2025"},"n_packages":2,"n_references":0,"next":{"headline":"Microweber CMS Authenticated Local File Inclusion via Backup API","id":"CVE-2025-34076"},"packages":[{"ecosystem":"RubyGems","fixed":["2.4.7"],"introduced":["2.2.10"],"last_affected":[],"package":"vagrant","purl":null,"source":"GHSA-hqp6-mjw3-f586"},{"ecosystem":"RubyGems","fixed":["2.4.7"],"introduced":["2.2.10"],"last_affected":[],"package":"vagrant","purl":"pkg:gem/vagrant","source":"GHSA-hqp6-mjw3-f586"}],"prev":{"headline":"Lucee Admin Interface Authenticated Remote Code Execution via Scheduled Job File Write","id":"CVE-2025-34074"},"products":[],"published":"2025-07-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2025-07-16","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-34075/"}