VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

simple_form: vulnerability history, versions and safety

simple_form is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 53 releases, first recorded in Sep 2019. 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
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 simple_form vulnerabilities

Vulert verdict on simple_form 5.4.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.4.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 30 Sep 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 8,229 i
  • OpenSSF scorecard 3/10 i
  • Last release 9 months ago i
  • Licence MIT 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 simple_form, 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.4.1 05 Jan 2026 none MIT — Details →
5.4.0 24 Oct 2025 none MIT — Details →
5.3.1 24 May 2024 none MIT — Details →
5.3.0 11 Oct 2023 none MIT — Details →
5.2.0 29 Jan 2023 none MIT — Details →
5.1.0 09 Feb 2021 none MIT — Details →
5.0.3 30 Sep 2020 none MIT — Details →
5.0.2 06 Feb 2020 none MIT — Details →
5.0.1 04 Oct 2019 none MIT — Details →
5.0.0 27 Sep 2019 none MIT — Details →
4.1.0 22 Nov 2018 C1 MIT Yes Details →
4.0.1 18 May 2018 C1 MIT Yes Details →
4.0.0 11 Apr 2018 C1 MIT Yes Details →
3.5.1 15 Feb 2018 C1 MIT Yes Details →
3.5.0 17 May 2017 C1 MIT Yes Details →
3.4.0 06 Jan 2017 C1 MIT Yes Details →
3.3.1 26 Aug 2016 C1 MIT Yes Details →
3.3.0 25 Aug 2016 C1 MIT Yes Details →
3.2.1 20 Dec 2015 C1 MIT Yes Details →
3.2.0 22 Sep 2015 C1 MIT Yes Details →
3.1.1 30 Aug 2015 C1 MIT Yes Details →
3.0.4 30 Jul 2015 C1 MIT Yes Details →
2.1.3 02 Jul 2015 C1 — Yes Details →
2.1.2 25 Nov 2014 C1 — Yes Details →
3.0.3 25 Nov 2014 C1 MIT Yes Details →
3.1.0 25 Nov 2014 C1 MIT Yes Details →
3.1.0.rc2 08 Jul 2014 C1 MIT Yes Details →
3.1.0.rc1 14 Apr 2014 C1 MIT Yes Details →
3.0.2 09 Apr 2014 C1 MIT Yes Details →
3.0.1 29 Nov 2013 C1 MIT Yes Details →
2.1.1 29 Nov 2013 C1 — Yes Details →
3.0.0 21 Sep 2013 C1 MIT Yes Details →
3.0.0.rc 10 May 2013 C1 MIT Yes Details →
2.1.0 26 Feb 2013 C1 — Yes Details →
3.0.0.beta1 26 Feb 2013 C1 — Yes Details →
2.0.4 08 Oct 2012 C1 — Yes Details →
2.0.3 27 Sep 2012 C1 — Yes Details →
2.0.2 30 Apr 2012 C1 — Yes Details →
2.0.1 27 Feb 2012 C1 — Yes Details →
2.0.0 23 Feb 2012 C1 — Yes Details →
2.0.0.rc 01 Feb 2012 C1 — Yes Details →
1.5.2 24 Sep 2011 C1 — Yes Details →
1.5.1 16 Sep 2011 C1 — Yes Details →
1.5.0 08 Sep 2011 C1 — Yes Details →
1.4.2 27 Jun 2011 C1 — Yes Details →
1.4.1 14 Jun 2011 C1 — Yes Details →
1.4.0 18 May 2011 C1 — Yes Details →
1.3.1 07 Feb 2011 C1 — Yes Details →
1.3.0 08 Dec 2010 C1 — Yes Details →
1.0.4 08 Oct 2010 C1 — Yes Details →
1.0.3 31 Aug 2010 C1 — Yes Details →
1.2.2 27 Jul 2010 C1 — Yes Details →
1.0.2 24 Jul 2010 C1 — Yes Details →
1.2.1 24 Jul 2010 C1 — Yes Details →
1.0.1 01 Jul 2010 C1 — Yes Details →
1.2.0 24 May 2010 C1 — Yes Details →
1.1.3 03 Apr 2010 C1 — Yes Details →
1.1.2 16 Mar 2010 C1 — Yes Details →
1.1.1 19 Feb 2010 C1 — Yes Details →
1.1.0 07 Feb 2010 C1 — Yes Details →
1.0.0 06 Feb 2010 C1 — Yes Details →
0.5 24 Dec 2009 C1 — Yes Details →
0.4.0 09 Nov 2009 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 simple_form

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-16676: Improper Input Validation in simple_form 9.8 critical 5.0.0 30 Sep 2019

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 simple_form

Is simple_form safe to use?

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

Vulert scores simple_form 77/100, which reads as in good shape. 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 simple_form affected?

No. 5.4.1, 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 simple_form should I use?

5.4.1 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 simple_form have?

1 vulnerability is recorded for simple_form 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 simple_form vulnerabilities disclosed?

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

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