VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

saml2: vulnerability history, versions and safety

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

Vulert verdict on saml2 3.3.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 8 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 saml2, 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
3.3.1 23 Jan 2026 none MIT — Details →
3.3.0 21 Oct 2025 none MIT — Details →
3.2.4 13 Oct 2025 none MIT — Details →
3.2.3 16 Jul 2025 none MIT — Details →
3.2.2 10 Jul 2025 none MIT — Details →
3.2.1 30 May 2025 none MIT — Details →
3.2.0 24 Mar 2025 none MIT — Details →
3.1.10 25 Feb 2025 none MIT — Details →
3.1.9 06 Feb 2025 none MIT — Details →
3.1.8 13 Nov 2024 none MIT — Details →
3.1.7 08 Apr 2024 none MIT — Details →
3.1.6 26 Feb 2024 none MIT — Details →
3.1.5 23 Feb 2024 none MIT — Details →
3.1.4 06 Oct 2023 none MIT — Details →
3.1.3 06 Oct 2023 none MIT — Details →
3.1.2 21 Mar 2022 none MIT — Details →
3.1.1 28 Sep 2021 none MIT — Details →
3.1.0 02 Aug 2021 none MIT — Details →
3.0.11 08 Jan 2021 none MIT — Details →
3.0.10 11 Dec 2020 none MIT — Details →
3.0.9 21 Aug 2020 none MIT — Details →
3.0.8 30 Jul 2019 none MIT — Details →
3.0.7 17 Apr 2019 none MIT — Details →
3.0.6 16 Apr 2019 none MIT — Details →
3.0.5 14 Jan 2019 none MIT — Details →
3.0.4 02 Jan 2019 none MIT — Details →
3.0.2 10 Sep 2018 none MIT — Details →
3.0.1 07 Sep 2018 none MIT — Details →
3.0.0 29 Jun 2018 none MIT — Details →
2.2.12 25 Jun 2018 none MIT — Details →
2.2.11 23 Jun 2018 none MIT — Details →
2.2.10 21 Jun 2018 none MIT — Details →
2.2.9 18 Jun 2018 none MIT — Details →
2.2.8 12 Jun 2018 none MIT — Details →
2.2.7 06 Jun 2018 none MIT — Details →
2.2.6 05 Jun 2018 none MIT — Details →
2.2.5 02 Jun 2018 none MIT — Details →
2.2.4 02 Jun 2018 none MIT — Details →
2.2.3 25 Apr 2018 none MIT — Details →
2.2.2 24 Apr 2018 none MIT — Details →
2.2.1 09 Apr 2018 none MIT — Details →
2.2.0 04 Apr 2018 none MIT — Details →
2.1.0 02 Mar 2018 none MIT — Details →
2.0.2 17 Feb 2018 none MIT — Details →
2.0.1 17 Feb 2018 none MIT — Details →
2.0.0 19 Dec 2017 none MIT — Details →
1.1.5 16 Nov 2017 none MIT — Details →
1.1.4 16 Nov 2017 none MIT — Details →
1.1.3 18 Jul 2017 none MIT — Details →
1.1.2 24 Jun 2017 none MIT — Details →
1.1.1 08 Jun 2017 none MIT — Details →
1.1.0 02 May 2017 none MIT — Details →
1.0.10 27 Mar 2017 none MIT — Details →
1.0.9 23 Mar 2017 none MIT — Details →
1.0.8 06 Feb 2017 none MIT — Details →
1.0.7 25 May 2016 none MIT — Details →
1.0.6 28 Apr 2016 none MIT — Details →
1.0.5 01 Jul 2015 none MIT — Details →
1.0.4 15 May 2015 none MIT — Details →
1.0.3 25 Mar 2015 none MIT — Details →
1.0.2 25 Mar 2015 none MIT — Details →
1.0.1 24 Mar 2015 none MIT — Details →
1.0.0 20 Mar 2015 none MIT — 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

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for saml2

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 saml2

Is saml2 safe to use?

Vulert has no vulnerabilities on record for saml2 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 saml2's Vulert package health score?

Vulert scores saml2 94/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 saml2 affected?

No. 3.3.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 saml2 should I use?

3.3.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 saml2 have?

0 vulnerabilities are recorded for saml2 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 saml2 vulnerabilities disclosed?

0 vulnerabilities were recorded for saml2 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 saml2 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 saml2 for upcoming vulnerabilities?

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