VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

spring: vulnerability history, versions and safety

spring is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

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 spring vulnerabilities

Vulert verdict on spring 4.7.0 i

Updated on 23 Oct 2026

Good news: 4.7.0, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 4.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,815 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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 spring, 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
4.7.0 23 Jun 2026 none MIT — Details →
4.6.0 26 May 2026 none MIT — Details →
4.5.0 01 May 2026 none MIT — Details →
4.4.2 03 Feb 2026 none MIT — Details →
4.4.1 03 Feb 2026 none MIT — Details →
4.4.0 07 Aug 2025 none MIT — Details →
4.3.0 12 Mar 2025 none MIT — Details →
4.2.1 22 Apr 2024 none MIT — Details →
4.2.0 09 Apr 2024 none MIT — Details →
4.1.3 22 Nov 2023 none MIT — Details →
4.1.2 14 Nov 2023 none MIT — Details →
4.1.1 09 Jan 2023 none MIT — Details →
4.1.0 21 Sep 2022 none MIT — Details →
4.0.0 10 Dec 2021 none MIT — Details →
3.1.1 25 Nov 2021 none MIT — Details →
3.1.0 23 Nov 2021 none MIT — Details →
3.0.0 08 Sep 2021 none MIT — Details →
2.1.1 25 Aug 2020 none MIT — Details →
2.1.0 14 Jun 2019 none MIT — Details →
2.0.2 21 May 2017 none MIT — Details →
2.0.1 21 Jan 2017 none MIT — Details →
2.0.0 01 Oct 2016 none MIT — Details →
1.7.2 01 Jul 2016 none MIT — Details →
1.7.1 11 Apr 2016 none MIT — Details →
1.7.0 10 Apr 2016 none MIT — Details →
1.6.4 26 Feb 2016 none MIT — Details →
1.6.3 04 Feb 2016 none MIT — Details →
1.6.2 08 Jan 2016 none MIT — Details →
1.6.1 22 Dec 2015 none MIT — Details →
1.6.0 14 Dec 2015 none MIT — Details →
1.5.0 30 Nov 2015 none MIT — Details →
1.4.4 18 Nov 2015 none MIT — Details →
1.4.3 17 Nov 2015 none MIT — Details →
1.4.2 16 Nov 2015 none MIT — Details →
1.4.1 10 Nov 2015 none MIT — Details →
1.4.0 12 Sep 2015 none MIT — Details →
1.3.6 08 May 2015 none MIT — Details →
1.3.5 29 Apr 2015 none MIT — Details →
1.3.4 06 Apr 2015 none MIT — Details →
1.3.3 26 Feb 2015 none MIT — Details →
1.3.2 14 Feb 2015 none MIT — Details →
1.3.1 09 Feb 2015 none MIT — Details →
1.3.0 07 Feb 2015 none MIT — Details →
1.2.0 22 Nov 2014 none MIT — Details →
1.1.3 13 May 2014 none MIT — Details →
1.1.2 26 Feb 2014 none MIT — Details →
1.1.1 09 Feb 2014 none MIT — Details →
1.1.0 17 Jan 2014 none MIT — Details →
1.1.0.beta4 13 Jan 2014 none MIT — Details →
1.1.0.beta3 13 Jan 2014 none MIT — Details →
1.1.0.beta2 12 Jan 2014 none MIT — Details →
1.1.0.beta1 03 Jan 2014 none MIT — Details →
1.0.0 19 Nov 2013 none MIT — Details →
0.9.2 10 Nov 2013 none — — Details →
0.9.1 09 Nov 2013 none — — Details →
0.9.0 27 Oct 2013 none — — Details →
0.0.11 09 Oct 2013 none — — Details →
0.0.10 21 Jun 2013 none — — Details →
0.0.9 09 Jun 2013 none — — Details →
0.0.8 22 Mar 2013 none — — Details →
0.0.7 24 Feb 2013 none — — Details →
0.0.6 07 Feb 2013 none — — Details →
0.0.5 26 Jan 2013 none — — Details →
0.0.4 13 Jan 2013 none — — Details →
0.0.3 11 Jan 2013 none — — Details →
0.0.2 29 Dec 2012 none — — Details →
0.0.1 29 Dec 2012 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for spring

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 spring

Is spring safe to use?

Vulert has no vulnerabilities on record for spring in RubyGems at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is spring's Vulert package health score?

Vulert scores spring 83/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 spring affected?

No. 4.7.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 spring should I use?

4.7.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 spring have?

0 vulnerabilities are recorded for spring in the RubyGems ecosystem: 0 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 spring vulnerabilities disclosed?

0 vulnerabilities were recorded for spring in the last 12 months. 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 spring 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 spring for upcoming vulnerabilities?

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