VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

foreman: vulnerability history, versions and safety

foreman is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Sep 2023. 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 C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 foreman vulnerabilities

Vulert verdict on foreman 0.90.0 i

Updated on 23 Oct 2026

Careful: 0.90.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.90.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 22 Sep 2023 i
  • Highest CVSS 9.1 i
  • With no published fix 1 i
  • Last release 14 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 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 foreman, 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
0.90.0 27 Jul 2025 C1 MIT No Details →
0.89.1 26 Jul 2025 C1 MIT No Details →
0.88.1 12 Apr 2024 C1 MIT No Details →
0.87.2 07 Aug 2020 C1 MIT No Details →
0.87.1 02 Apr 2020 C1 MIT No Details →
0.87.0 07 Jan 2020 C1 MIT No Details →
0.86.0 09 Oct 2019 C1 MIT No Details →
0.85.0 18 Jun 2018 C1 MIT No Details →
0.84.0 28 Mar 2017 C1 MIT No Details →
0.83.0 18 Jan 2017 C1 MIT No Details →
0.82.0 21 May 2016 C1 MIT No Details →
0.81.0 26 Apr 2016 C1 MIT No Details →
0.80.2 24 Apr 2016 C1 MIT No Details →
0.80.1 23 Apr 2016 C1 MIT No Details →
0.80.0 23 Apr 2016 C1 MIT No Details →
0.78.0 13 Mar 2015 C1 MIT No Details →
0.77.0 02 Jan 2015 C1 MIT No Details →
0.76.0 26 Nov 2014 C1 MIT No Details →
0.75.0 27 Aug 2014 C1 MIT No Details →
0.74.0 19 Jun 2014 C1 MIT No Details →
0.73.0 19 Jun 2014 C1 MIT No Details →
0.71.0 03 Jun 2014 C1 MIT No Details →
0.70.0 03 Jun 2014 C1 MIT No Details →
0.69.0 03 Jun 2014 C1 MIT No Details →
0.67.0 24 Apr 2014 C1 MIT No Details →
0.66.0 24 Apr 2014 C1 MIT No Details →
0.65.0 23 Apr 2014 C1 MIT No Details →
0.64.0 22 Apr 2014 C1 MIT No Details →
0.63.0 15 Apr 2013 C1 MIT No Details →
0.62.0 08 Mar 2013 C1 MIT No Details →
0.61.0 14 Jan 2013 C1 MIT No Details →
0.60.2 08 Oct 2012 C1 — No Details →
0.60.0 25 Sep 2012 C1 — No Details →
0.59.0 15 Sep 2012 C1 — No Details →
0.58.0 14 Sep 2012 C1 — No Details →
0.57.0 21 Aug 2012 C1 — No Details →
0.56.0 19 Aug 2012 C1 — No Details →
0.55.0 14 Aug 2012 C1 — No Details →
0.54.0 14 Aug 2012 C1 — No Details →
0.53.0 24 Jul 2012 C1 — No Details →
0.52.0 24 Jul 2012 C1 — No Details →
0.51.0 11 Jul 2012 C1 — No Details →
0.50.0 11 Jul 2012 C1 — No Details →
0.49.0 11 Jul 2012 C1 — No Details →
0.48.0 10 Jul 2012 C1 — No Details →
0.48.0.pre3 18 Jun 2012 C1 — No Details →
0.48.0.pre2 18 Jun 2012 C1 — No Details →
0.48.0.pre1 11 Jun 2012 C1 — No Details →
0.47.0 08 Jun 2012 C1 — No Details →
0.46.0 02 May 2012 C1 — No Details →
0.45.0 26 Apr 2012 C1 — No Details →
0.44.0 23 Apr 2012 C1 — No Details →
0.43.0 20 Apr 2012 C1 — No Details →
0.42.0 18 Apr 2012 C1 — No Details →
0.41.0 16 Mar 2012 C1 — No Details →
0.40.0 24 Feb 2012 C1 — No Details →
0.39.0 07 Feb 2012 C1 — No Details →
0.38.0 02 Feb 2012 C1 — No Details →
0.37.2 30 Jan 2012 C1 — No Details →
0.37.1 29 Jan 2012 C1 — No Details →
0.37.0 29 Jan 2012 C1 — No Details →
0.37.0.pre5 24 Jan 2012 C1 — No Details →
0.37.0.pre4 24 Jan 2012 C1 — No Details →
0.37.0.pre3 23 Jan 2012 C1 — No Details →
0.37.0.pre2 23 Jan 2012 C1 — No Details →
0.37.0.pre1 22 Jan 2012 C1 — No Details →
0.36.1 18 Jan 2012 C1 — No Details →
0.36.0 18 Jan 2012 C1 — No Details →
0.35.0 16 Jan 2012 C1 — No Details →
0.34.1 16 Jan 2012 C1 — No Details →
0.34.0 16 Jan 2012 C1 — No Details →
0.33.1 16 Jan 2012 C1 — No Details →
0.33.0 15 Jan 2012 C1 — No Details →
0.32.0 12 Jan 2012 C1 — No Details →
0.31.0 04 Jan 2012 C1 — No Details →
0.30.1 23 Dec 2011 C1 — No Details →
0.30.0 22 Dec 2011 C1 — No Details →
0.29.0 22 Dec 2011 C1 — No Details →
0.28.0.pre2 09 Dec 2011 C1 — No Details →
0.28.0.pre1 09 Dec 2011 C1 — No Details →
0.27.0 05 Dec 2011 C1 — No Details →
0.26.1 10 Nov 2011 C1 — No Details →
0.26.0 08 Nov 2011 C1 — No Details →
0.25.0 17 Oct 2011 C1 — No Details →
0.24.0 04 Oct 2011 C1 — No Details →
0.23.1 04 Oct 2011 C1 — No Details →
0.22.0 13 Sep 2011 C1 — No Details →
0.21.0 09 Sep 2011 C1 — No Details →
0.20.0 22 Aug 2011 C1 — No Details →
0.19.0 27 Jun 2011 C1 — No Details →
0.18.0 03 Jun 2011 C1 — No Details →
0.17.0 02 Jun 2011 C1 — No Details →
0.16.0 13 May 2011 C1 — No Details →
0.15.0 12 May 2011 C1 — No Details →
0.14.0 12 May 2011 C1 — No Details →
0.13.1 10 May 2011 C1 — No Details →
0.13.0 07 May 2011 C1 — No Details →
0.12.0 01 Apr 2011 C1 — No Details →
0.12.0.pre1 25 Mar 2011 C1 — No Details →
0.11.1 08 Mar 2011 C1 — No Details →
0.11.0 28 Jan 2011 C1 — No Details →
0.10.1 22 Dec 2010 C1 — No Details →
0.10.0 13 Dec 2010 C1 — No Details →
0.9.2 09 Nov 2010 C1 — No Details →
0.9.1 03 Nov 2010 C1 — No Details →
0.9.0 03 Nov 2010 C1 — No Details →
0.9.0.beta.1 15 Oct 2010 C1 — No Details →
0.8.0 20 Sep 2010 C1 — No Details →
0.7.5 17 Sep 2010 C1 — No Details →
0.7.4 17 Sep 2010 C1 — No Details →
0.7.3 24 Aug 2010 C1 — No Details →
0.7.2 24 Aug 2010 C1 — No Details →
0.7.1 20 Jul 2010 C1 — No Details →
0.7.0 20 Jul 2010 C1 — No Details →
0.6.0 06 Jul 2010 C1 — No Details →
0.5.1 01 Jul 2010 C1 — No Details →
0.5.0 01 Jul 2010 C1 — No Details →
0.4.7 29 Jun 2010 C1 — No Details →
0.4.6 29 Jun 2010 C1 — No Details →
0.4.5 29 Jun 2010 C1 — No Details →

The newest 120 of 132 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 foreman

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-38749: Denial of Service in snakeYAML 9.1 critical No fix published 22 Sep 2023

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 foreman

Is foreman safe to use?

Vulert records 1 vulnerabilities for foreman in RubyGems: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is foreman's Vulert package health score?

Vulert scores foreman 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of foreman affected?

Yes. 0.90.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of foreman should I use?

0.90.0 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 foreman have?

1 vulnerability is recorded for foreman in the RubyGems ecosystem: 1 critical, 0 high, 0 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 foreman vulnerabilities disclosed?

0 vulnerabilities were recorded for foreman in the last 12 months, and the oldest entry in this database dates to 22 Sep 2023. 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 foreman 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 foreman for upcoming vulnerabilities?

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