ruby-saml (rubygems) has 10 known vulnerabilities, the worst rated CRITICAL. Upgrade to 1.18.1 or later to clear all of them. No malicious-package signal is recorded.
Ruby-saml up to and including 1.12.4, there is an authentication bypass vulnerability because of an issue at libxml2 canonicalization process used by Nokogiri…
CyberXYZ does not call a package safe in absolute terms. It records 10 known vulnerabilities for ruby-saml (rubygems), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does ruby-saml have known vulnerabilities?
Yes. CyberXYZ records 10 known vulnerabilities for ruby-saml (rubygems), the worst rated CRITICAL. These include GHSA-x4h9-gwv3-r4m4, GHSA-9v8j-x534-2fx3, GHSA-4vc4-m8qh-g8jm, GHSA-754f-8gm6-c4r2, GHSA-jw9c-mfg7-9rx2.
Which version of ruby-saml should I use?
1.18.1 or later clears every advisory recorded for ruby-saml (rubygems). Check the release you pick before installing it.
How do I check ruby-saml before installing?
Search ruby-saml in CyberXYZ Check at https://cyberxyz.io/check?q=ruby-saml. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:47 UTC. The most recent advisory here was published 2025-12-08. Updated continuously from NVD, GHSA, OSV and CNA feeds.