VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ruby-saml: vulnerability history, versions and safety

ruby-saml is a package in the Debian ecosystem. Vulert records 19 vulnerabilities for it across 3 releases, from Jan 2017 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
19 vulnerabilities recorded U19
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 ruby-saml vulnerabilities

Vulert verdict on ruby-saml i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Sep 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 19 vulnerabilities on record across 8 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 19 over 8 years · 0 in the last year i
  • Latest disclosure 01 Sep 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

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 holds for ruby-saml, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.11.0-1 U13 Yes Details →
1.11.0-1+deb11u2 U3 Yes Details →
1.11.0-1+deb11u1 U10 Yes Details →

Newest 3 of 3 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2019 2
  • 2023 2
  • 2024 3
  • 2025 10

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 19 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ruby-saml

The 5 most severe of 19 vulnerabilities recorded for this package

Search all 19 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
XPath Injection Vulnerability in ruby-saml Package 9.8 critical 1.0.0-1 27 May 2023
Critical SAML Data Manipulation Vulnerability in OneLogin Ruby-SAML Package 9.8 critical 1.7.2-1 17 Apr 2019
Critical Signature Verification Flaw in Ruby SAML Library 9.8 critical 1.11.0-1+deb11u1 10 Sep 2024
Authentication Bypass Vulnerability in ruby-saml: A Critical Security Flaw 9.8 critical 1.11.0-1+deb11u2 12 Mar 2025
Authentication Bypass Vulnerability in ruby-saml: Signature Wrapping Attack 9.8 critical 1.11.0-1+deb11u2 12 Mar 2025

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 ruby-saml

Is ruby-saml safe to use?

Vulert records 19 vulnerabilities for ruby-saml in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 19 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does ruby-saml have?

19 vulnerabilities are recorded for ruby-saml in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 19 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ruby-saml vulnerabilities disclosed?

0 vulnerabilities were recorded for ruby-saml in the last 12 months, and the oldest entry in this database dates to 23 Jan 2017. 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 ruby-saml 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 ruby-saml for upcoming vulnerabilities?

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