Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Critical

Authentication bypass (Signature Wrapping) in ruby-saml (ReXML vs Nokogiri parser discrepancy)

IdentifiersCVE-2025-66567CWE-347· Improper Verification of…

CVE-2025-66567 is an authentication bypass in the ruby-saml library (client-side SAML implementation) affecting versions up to and including 1.12.4. The issue stems from an incomplete fix for CVE-2025-25292 and a fragile multi-parser design: ReXML and Nokogiri/libxml2 parse the same XML into different document structures. ruby-saml uses these parsers for different parts of XML Signature processing (e.g., locating/reading signature-related values vs. processing/transforms/canonicalization of signed content), enabling an attacker to craft a SAML Response that passes signature verification while the application consumes an attacker-controlled Assertion. This is a Signature Wrapping-style attack enabled by parser inconsistencies.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote authentication bypass in applications relying on ruby-saml for SAML SSO, by desynchronizing XML Signature verification from the assertion/business-logic parsing. An attacker can potentially log in as an arbitrary user (or otherwise obtain an authenticated session) without possessing valid credentials, depending on the service provider’s SAML integration and attribute mapping.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure of SAML endpoints to untrusted networks where feasible and add compensating controls around SSO (e.g., additional access policies/conditional access) to limit impact of an SSO bypass. However, given the nature of signature verification bypass, the effective mitigation is updating to a fixed ruby-saml release.

Remediation

Patch, then assume compromise.

Upgrade ruby-saml to version 1.18.0 or later, which fixes CVE-2025-66567. Ensure deployments are not pinned to vulnerable versions (<= 1.12.4) and that downstream applications redeploy with the updated dependency.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OneLoginRuby-Samlapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.