Is ruby-saml 0.8 vulnerable?
RubyGems · 19 releases from 0.8.0 to 0.8.18 · latest ruby-saml is 1.18.1 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. ruby-saml 0.8.18, the last 0.8 release, is affected by 10 known security advisories (6 critical, 3 high, 1 medium), including CVE-2025-66568, CVE-2025-66567, CVE-2025-25292. Upgrade to 1.18.1 or later to fix all of them.
bundle update --conservative ruby-saml # Gemfile: '>= 1.18.1'Is your project on an affected ruby-saml?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting ruby-saml 0.8.18
Ruby-saml allows a Libxml2 Canonicalization error to bypass Digest/Signature validation
- Affected
- <1.18.0
- Fixed in
- 1.18.0
Ruby-saml has a SAML authentication bypass due to namespace handling (parser differential)
- Affected
- <1.18.0
- Fixed in
- 1.18.0
Ruby SAML DOS vulnerability with large SAML response
- Affected
- <1.18.1
- Fixed in
- 1.18.1
Ruby SAML allows a SAML authentication bypass due to namespace handling (parser differential)
- Affected
- >=1.13.0 <1.18.0 · <1.12.4
- Fixed in
- 1.12.4, 1.18.0
Ruby SAML allows a SAML authentication bypass due to DOCTYPE handling (parser differential)
- Affected
- <1.12.4 · >=1.13.0 <1.18.0
- Fixed in
- 1.12.4, 1.18.0
Ruby SAML allows remote Denial of Service (DoS) with compressed SAML responses
- Affected
- <1.12.4 · >=1.13.0 <1.18.0
- Fixed in
- 1.12.4, 1.18.0
SAML authentication bypass via Incorrect XPath selector
- Affected
- <1.12.3 · >=1.13.0 <1.17.0
- Fixed in
- 1.12.3, 1.17.0
ruby-saml vulnerable to XPath injection
- Affected
- <1.0.0
- Fixed in
- 1.0.0
Ruby-SAML Improper Authentication vulnerability
- Affected
- <1.7.0
- Fixed in
- 1.7.0
Ruby-saml allows attackers to perform XML signature wrapping attacks
- Affected
- <1.3.0
- Fixed in
- 1.3.0
Every ruby-saml 0.8.x release
Affected: 0.8.0 to 0.8.18. Latest ruby-saml: 1.18.1.
| Version | Known advisories |
|---|---|
| ruby-saml 0.8.18 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.17 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.16 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.15 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.14 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.13 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.12 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.11 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.10 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.9 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.8 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.7 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.6 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.5 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.4 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.3 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.2 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.1 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
| ruby-saml 0.8.0 | CVE-2025-66568, CVE-2025-66567, CVE-2025-54572, CVE-2025-25292, CVE-2025-25291, CVE-2025-25293, CVE-2024-45409, CVE-2015-20108, CVE-2017-11428, CVE-2016-5697 |
Which of your client projects are still on ruby-saml 0.8?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ruby-saml version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other ruby-saml versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.