CVE-2025-66568: ruby-saml · Improper Verification of Cryptographic Signature
Affects ruby-samlSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.18.0 as a priority.
Data as of 15 Nov 2026, 20:25 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.18.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade ruby-saml to 1.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAML-Toolkits ruby-saml | Affected
| Fixed in
|
AI-suggested
The primary mitigation is to upgrade ruby-saml to version 1.18.0 or later, where the vulnerability is fixed. Organizations should audit their software dependencies to identify and remediate any usage of vulnerable ruby-saml versions. Additionally, implement strict XML input validation and sanitization to prevent malformed XML from triggering the canonicalization flaw. Employ defense-in-depth by monitoring authentication logs for anomalies indicative of signature wrapping or authentication bypass attempts. Consider deploying Web Application Firewalls (WAFs) with rules targeting suspicious SAML assertions. Regularly update and patch all components involved in SAML processing, including Nokogiri and libxml2, to ensure no residual vulnerabilities remain. Conduct penetration testing focused on SAML authentication flows to detect potential exploitation. Finally, educate developers and security teams about the risks of improper signature verification and the importance of secure XML handling.
Description
The ruby-saml library implements the client side of an SAML authorization. Versions up to and including 1.12.4, are vulnerable to authentication bypass through the libxml2 canonicalization process used by Nokogiri for document transformation, which allows an attacker to execute a Signature Wrapping attack. When libxml2’s canonicalization is invoked on an invalid XML input, it may return an empty string rather than a canonicalized node.ruby-saml then proceeds to compute the DigestValue over this empty string, treating it as if canonicalization succeeded. This issue is fixed in version 1.18.0.