VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

vagrant: vulnerability history, versions and safety

vagrant is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vagrant vulnerabilities

Vulert verdict on vagrant 2.4.9 i

Updated on 23 Oct 2026

Good news: 2.4.9, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 85/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2.4.9 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.4.9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.4.9 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 02 Jul 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 27,218 i
  • OpenSSF scorecard 5/10 i
  • Last release 14 months ago i
  • Licence BUSL-1.1 i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for vagrant, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.4.9 21 Aug 2025 none BUSL-1.1 — Details →
2.4.8 05 Aug 2025 none BUSL-1.1 — Details →
2.4.7 17 Jun 2025 none BUSL-1.1 — Details →
2.4.6 22 May 2025 M1 BUSL-1.1 Yes Details →
2.4.5 23 Apr 2025 M1 BUSL-1.1 Yes Details →
2.4.4 21 Apr 2025 M1 BUSL-1.1 Yes Details →
1.5.0 13 Mar 2014 none MIT — Details →
1.0.7 14 Mar 2013 none — — Details →
1.0.6 24 Jan 2013 none — — Details →
1.0.5 19 Sep 2012 none — — Details →
1.0.4 14 Sep 2012 none — — Details →
1.0.3 02 May 2012 none — — Details →
1.0.2 25 Mar 2012 none — — Details →
1.0.1 12 Mar 2012 none — — Details →
1.0.0 06 Mar 2012 none — — Details →
0.9.7 09 Feb 2012 none — — Details →
0.9.5 05 Feb 2012 none — — Details →
0.9.4 29 Jan 2012 none — — Details →
0.9.3 24 Jan 2012 none — — Details →
0.9.2 20 Jan 2012 none — — Details →
0.9.1 18 Jan 2012 none — — Details →
0.9.0 17 Jan 2012 none — — Details →
0.8.10 11 Dec 2011 none — — Details →
0.8.8 02 Dec 2011 none — — Details →
0.8.7 13 Sep 2011 none — — Details →
0.8.6 29 Aug 2011 none — — Details →
0.8.5 16 Aug 2011 none — — Details →
0.8.2 23 Jul 2011 none — — Details →
0.8.1 21 Jul 2011 none — — Details →
0.7.8 19 Jul 2011 none — — Details →
0.7.7 13 Jul 2011 none — — Details →
0.7.6 03 Jul 2011 none — — Details →
0.7.5 16 May 2011 none — — Details →
0.7.4 12 May 2011 none — — Details →
0.7.3 20 Apr 2011 none — — Details →
0.7.2 09 Feb 2011 none — — Details →
0.7.1 29 Jan 2011 none — — Details →
0.7.0 19 Jan 2011 none — — Details →
0.7.0.beta2 14 Jan 2011 none — — Details →
0.7.0.beta 25 Dec 2010 none — — Details →
0.6.9 22 Dec 2010 none — — Details →
0.6.8 01 Dec 2010 none — — Details →
0.6.7 04 Nov 2010 none — — Details →
0.6.6 14 Oct 2010 none — — Details →
0.6.5 08 Oct 2010 none — — Details →
0.6.4 05 Oct 2010 none — — Details →
0.6.3 27 Sep 2010 none — — Details →
0.6.2 27 Sep 2010 none — — Details →
0.6.1 27 Sep 2010 none — — Details →
0.6.0 27 Sep 2010 none — — Details →
0.5.4 07 Sep 2010 none — — Details →
0.5.3 24 Aug 2010 none — — Details →
0.5.2 04 Aug 2010 none — — Details →
0.5.1 31 Jul 2010 none — — Details →
0.5.0 26 Jul 2010 none — — Details →
0.4.2 02 Jul 2010 none — — Details →
0.4.1 18 Jun 2010 none — — Details →
0.4.0 10 Jun 2010 none — — Details →
0.3.4 22 May 2010 none — — Details →
0.3.3 13 May 2010 none — — Details →
0.3.2 24 Apr 2010 none — — Details →
0.3.1 22 Apr 2010 none — — Details →
0.3.0 16 Apr 2010 none — — Details →
0.2.0 16 Mar 2010 none — — Details →
0.2.0.pre 15 Mar 2010 none — — Details →
0.1.4 10 Mar 2010 none — — Details →
0.1.4.pre.a 09 Mar 2010 none — — Details →
0.1.3 09 Mar 2010 none — — Details →
0.1.2 09 Mar 2010 none — — Details →
0.1.1 08 Mar 2010 none — — Details →
0.1.0 08 Mar 2010 none — — Details →

All 71 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for vagrant

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-34075: HashiCorp Vagrant Code Injection Vulnerability via Default Synced Folders N/A medium 2.4.7 02 Jul 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About vagrant

Is vagrant safe to use?

Vulert records 1 vulnerabilities for vagrant in RubyGems: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is vagrant's Vulert package health score?

Vulert scores vagrant 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of vagrant affected?

No. 2.4.9, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of vagrant should I use?

2.4.9 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does vagrant have?

1 vulnerability is recorded for vagrant in the RubyGems ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new vagrant vulnerabilities disclosed?

0 vulnerabilities were recorded for vagrant in the last 12 months, and the oldest entry in this database dates to 02 Jul 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of vagrant are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor vagrant for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the vagrant version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.