VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

hammer_cli_foreman: vulnerability history, versions and safety

hammer_cli_foreman is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 31 releases, first recorded in May 2022. 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 H1
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 hammer_cli_foreman vulnerabilities

Vulert verdict on hammer_cli_foreman 5.0.0 i

Updated on 23 Oct 2026

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

Package health score 95/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 5.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Last release 2 months ago i
  • Licence GPL-3.0-or-later 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 hammer_cli_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
5.0.0 11 Aug 2026 none GPL-3.0-or-later — Details →
3.19.0 11 May 2026 none GPL-3.0-or-later — Details →
3.18.1 04 Mar 2026 none GPL-3.0-or-later — Details →
3.18.0 10 Feb 2026 none GPL-3.0-or-later — Details →
3.17.0 11 Nov 2025 none GPL-3.0-or-later — Details →
3.16.0 13 Aug 2025 none GPL-3.0-or-later — Details →
3.15.0 14 May 2025 none GPL-3.0-or-later — Details →
3.14.1 31 Mar 2025 none GPL-3.0-or-later — Details →
3.14.0 20 Feb 2025 none GPL-3.0-or-later — Details →
3.13.0 08 Nov 2024 none GPL-3.0+ — Details →
3.12.0 14 Aug 2024 none GPL-3.0+ — Details →
3.11.0 22 May 2024 none GPL-3.0+ — Details →
3.10.0 21 Feb 2024 none GPL-3.0+ — Details →
3.9.0 29 Nov 2023 none GPL-3.0+ — Details →
3.8.0 25 Aug 2023 none GPL-3.0+ — Details →
3.7.0 23 May 2023 none GPL-3.0+ — Details →
3.5.1 28 Feb 2023 none GPL-3.0+ — Details →
3.6.0 23 Feb 2023 none GPL-3.0+ — Details →
3.5.0 31 Oct 2022 none GPL-3.0+ — Details →
3.4.0 09 Aug 2022 none GPL-3.0+ — Details →
3.3.0 10 May 2022 none GPL-3.0+ — Details →
3.2.0 10 Feb 2022 none GPL-3.0+ — Details →
2.5.2 01 Feb 2022 none GPL-3.0+ — Details →
3.1.0 10 Nov 2021 none GPL-3.0+ — Details →
3.0.0 04 Aug 2021 none GPL-3.0+ — Details →
2.5.1 08 Jun 2021 none GPL-3.0+ — Details →
2.5.0 04 May 2021 none GPL-3.0+ — Details →
2.3.2 04 May 2021 none GPL-3.0+ — Details →
2.4.0 02 Feb 2021 none GPL-3.0+ — Details →
2.3.1 27 Jan 2021 none GPL-3.0+ — Details →
2.3.0 03 Nov 2020 none GPL-3.0+ — Details →
2.1.3 04 Sep 2020 none GPL-3.0+ — Details →
2.2.0 11 Aug 2020 none GPL-3.0+ — Details →
2.1.2 14 Jul 2020 none GPL-3.0+ — Details →
2.1.1 29 May 2020 none GPL-3.0+ — Details →
2.1.0 14 May 2020 none GPL-3.0+ — Details →
2.0.2 24 Mar 2020 none GPL-3.0+ — Details →
2.0.1 25 Feb 2020 none GPL-3.0+ — Details →
2.0.0 12 Feb 2020 none GPL-3.0+ — Details →
0.19.7 16 Jan 2020 none GPL-3.0+ — Details →
0.19.6 10 Jan 2020 none GPL-3.0+ — Details →
0.19.5 31 Dec 2019 none GPL-3.0+ — Details →
0.19.4 09 Dec 2019 none GPL-3.0+ — Details →
0.19.3 04 Dec 2019 none GPL-3.0+ — Details →
0.19.2 25 Nov 2019 none GPL-3.0+ — Details →
0.18.2 18 Nov 2019 none GPL-3.0+ — Details →
0.19.1 18 Nov 2019 none GPL-3.0+ — Details →
0.18.1 31 Oct 2019 none GPL-3.0+ — Details →
0.19.0 26 Oct 2019 none GPL-3.0+ — Details →
0.17.2 13 Aug 2019 none GPL-3.0+ — Details →
0.18.0 01 Aug 2019 none GPL-3.0+ — Details →
0.17.1 10 Jul 2019 none GPL-3.0+ — Details →
0.17.0 24 Apr 2019 none GPL-3.0+ — Details →
0.15.2 17 Apr 2019 none GPL-3.0+ — Details →
0.16.0 16 Jan 2019 none GPL-3.0+ — Details →
0.15.1 06 Nov 2018 none GPL-3.0+ — Details →
0.15.0 24 Oct 2018 none GPL-3.0+ — Details →
0.14.0 27 Aug 2018 none non-standard — Details →
0.13.2 15 Aug 2018 none non-standard — Details →
0.13.1 16 Jul 2018 none non-standard — Details →
0.13.0 09 May 2018 none non-standard — Details →
0.12.1 05 Mar 2018 none non-standard — Details →
0.12.0 19 Feb 2018 none non-standard — Details →
0.11.0 01 Aug 2017 none non-standard — Details →
0.10.2 05 May 2017 none non-standard — Details →
0.10.1 25 Apr 2017 none non-standard — Details →
0.10.0 28 Mar 2017 none non-standard — Details →
0.9.0 15 Dec 2016 H1 non-standard Yes Details →
0.8.0 01 Sep 2016 H1 non-standard Yes Details →
0.7.0 14 Jun 2016 H1 non-standard Yes Details →
0.6.2 22 Mar 2016 H1 non-standard Yes Details →
0.6.1 15 Mar 2016 H1 non-standard Yes Details →
0.6.0 25 Feb 2016 H1 non-standard Yes Details →
0.5.1 14 Dec 2015 H1 non-standard Yes Details →
0.5.0 14 Dec 2015 H1 non-standard Yes Details →
0.4.0 21 Sep 2015 H1 non-standard Yes Details →
0.3.0 29 Jul 2015 H1 non-standard Yes Details →
0.2.0 23 Apr 2015 H1 non-standard Yes Details →
0.1.4 11 Dec 2014 H1 non-standard Yes Details →
0.1.3 20 Aug 2014 H1 non-standard Yes Details →
0.1.2 13 Aug 2014 H1 non-standard Yes Details →
0.1.1 20 May 2014 H1 non-standard Yes Details →
0.1.0 26 Mar 2014 H1 non-standard Yes Details →
0.0.18 29 Jan 2014 H1 non-standard Yes Details →
0.0.17 23 Jan 2014 H1 non-standard Yes Details →
0.0.16 21 Jan 2014 H1 non-standard Yes Details →
0.0.15 19 Dec 2013 H1 non-standard Yes Details →
0.0.14 19 Dec 2013 H1 — Yes Details →
0.0.13 18 Dec 2013 H1 — Yes Details →
0.0.12 05 Dec 2013 H1 — Yes Details →
0.0.11 26 Nov 2013 H1 — Yes Details →
0.0.10 08 Nov 2013 H1 — Yes Details →
0.0.9 29 Oct 2013 H1 — Yes Details →
0.0.8 23 Oct 2013 H1 — Yes Details →
0.0.7 10 Oct 2013 H1 — Yes Details →
0.0.6 08 Oct 2013 H1 — Yes Details →
0.0.5 26 Sep 2013 H1 — Yes Details →
0.0.4 30 Aug 2013 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 hammer_cli_foreman

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-2667: hammer_cli_foreman Improper Certificate Validation vulnerability 8.1 high 0.10.0 13 May 2022

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 hammer_cli_foreman

Is hammer_cli_foreman safe to use?

Vulert records 1 vulnerabilities for hammer_cli_foreman in RubyGems: 0 critical, 1 high, 0 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 hammer_cli_foreman's Vulert package health score?

Vulert scores hammer_cli_foreman 95/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 hammer_cli_foreman affected?

No. 5.0.0, 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 hammer_cli_foreman should I use?

5.0.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 hammer_cli_foreman have?

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

0 vulnerabilities were recorded for hammer_cli_foreman in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 hammer_cli_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 hammer_cli_foreman for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the hammer_cli_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.