Skip to content
Fencer Intel
no cvss —

CVE-2025-34075 json

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

published last yr. modified last yr.

Withdrawn or rejected on

Its source no longer considers this a valid vulnerability. It stays here so links keep working, and it is left out of feeds.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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

Is CVE-2025-34075 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-34075 updated

vagrant: HashiCorp Vagrant Host Code Execution

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.