ruby-saml vulnerable to SAML authentication bypass due to DOCTYPE handling (parser differential)

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• netapp storagegridall versions
• omniauth omniauth samlbefore 1.10.6
• omniauth omniauth saml2.0.0 and later · before 2.1.3
• omniauth omniauth saml2.2.0 and later · before 2.2.3
• onelogin ruby-samlbefore 1.12.4
• onelogin ruby-saml1.13.0 and later · before 1.18.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• SAML-Toolkits ruby-saml

  • < 1.12.4, >= 1.13.0, < 1.18.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2025-25292Ruby SAML vulnerable to SAML authentication bypass due to namespace handling (parser differential)
  57Plan
• CVE-2017-11430Multiple SAML libraries may allow authentication bypass via incorrect XML canonicalization and DOM traversal
  40Plan
• CVE-2025-25293ruby-saml vulnerable to Remote Denial of Service (DoS) with compressed SAML responses
  30Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const claims = jwt.verify(token, publicKey);

1const claims = jwt.verify(token, publicKey, {2  algorithms: ["RS256"],3  issuer: "https://id.example.com",4  audience: "portal",5});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.