External risk intelligence

Ruby-SAML Authentication Bypass Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-66567

The ruby-saml library is a core component used to implement SAML authentication. Because SAML is fundamentally designed for identity federation and remote authentication across networks, services utilizing this library are typically public-facing, internet-reachable identity providers or service providers that must remain accessible to users or external systems to function.

Authentication Bypass

Onelogin Ruby Saml

before 1.18.0

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in the ruby-saml library, which handles client-side SAML authorization. The issue, stemming from an incomplete fix for a previous vulnerability, allows for authentication bypass through a Signature Wrapping attack, potentially impacting systems that rely on this library for secure identity federation.

  • Bypasses authentication.
  • SAML is a key identity standard.
  • Confirm if this library is used.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication by sending a specially crafted XML request to an application using the vulnerable ruby-saml library. This exploits a weakness in how XML is parsed, allowing the attacker to impersonate a legitimate user.

  • No authentication or privileges required.
  • XML parsing and signature validation.
  • Authentication bypass and unauthorized access.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could bypass authentication mechanisms within systems using the ruby-saml library by exploiting a signature wrapping vulnerability in XML parsing. This could allow unauthorized access to services that rely on SAML for authorization.

  • System authentication data at risk.
  • Signature wrapping attack may occur.
  • Unauthorized access to services.

Operational Fix

Recommended remediation, mitigation, and detection steps

The ownership of this vulnerability likely lies with the application teams managing SAML integrations, potentially in coordination with platform or infrastructure teams responsible for the underlying Ruby environment. The first practical step is to identify all systems using the ruby-saml library, confirm their business criticality and exposure, and then engage the accountable application owners to plan for remediation.

  • Application teams should own the issue.
  • Verify ruby-saml usage and exposure.
  • Plan remediation with application owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the ruby-saml library used for?

The ruby-saml library is a software component designed for Ruby applications to manage SAML-based authentication. It acts as a toolkit for service providers and identity providers to handle the exchange of XML-based identity data, enabling single sign-on capabilities where users can authenticate once to access multiple linked web services.

How does CVE-2025-66567 enable authentication bypass?

This vulnerability is classified as Improper Verification of Cryptographic Signature (CWE-347). It occurs because the library's XML parsing logic is inconsistent when using different parsers like ReXML and Nokogiri. This discrepancy allows an attacker to perform a Signature Wrapping attack, where they manipulate the XML structure so the application validates a legitimate signature while processing malicious, unauthorized user data.

Does this vulnerability require user interaction to trigger?

No, this flaw does not require user interaction or pre-existing privileges. An attacker simply needs to send a specially crafted XML request to an application that relies on the vulnerable library. The attack is triggered by the way the application processes these incoming XML documents during the authentication flow, rather than through any action performed by a legitimate user.

Why is my application at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a high-priority risk because ruby-saml is a core component for identity federation. Since SAML services must be reachable by external systems or users to facilitate logins, they are often exposed to the internet. If your application handles these authentication requests, it is likely in an environment where network-based attacks are feasible.

How should I respond to this ruby-saml vulnerability?

Begin by auditing your software inventory to locate instances where ruby-saml is implemented. Once identified, work with your application and infrastructure teams to assess the business impact of these services. The primary remediation is to update the library to version 1.18.0 or later, which contains the corrected logic to handle XML parsing consistently.

References