dbcve.org
Omniauth SamlApplication · Omniauth

CVE-2025-25292

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-12
Fix available
A fix is available. Upgrade to 1.10.6 / 1.12.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. An authentication bypass vulnerability was found in ruby-saml prior to versions 1.12.4 and 1.18.0 due to a parser differential. ReXML and Nokogiri parse XML differently, the parsers can generate entirely different document structures from the same XML input. That allows an attacker to be able to execute a Signature Wrapping attack. This issue may lead to authentication bypass. Versions 1.12.4 and 1.18.0 contain a patch for the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-347

The application accepts signed data without properly verifying the signature, so an attacker can forge or tamper with content that the system is meant to trust — tokens, updates, licences. Everything built on that trust then becomes unreliable. Remediation is verifying every signature against the correct key and rejecting anything that does not validate.

General guidance for the improper signature verification class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Omniauth SamlApplication
Affected:< 1.10.6>= 2.0.0, < 2.1.3>= 2.2.0, < 2.2.3
Ruby SamlApplication
Affected:< 1.12.4>= 1.13.0, < 1.18.0
StoragegridApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.6 / 1.12.4 / 1.18.0 or later
Fixed in 1.10.61.12.41.18.0
Vendor patch about.gitlab.com →
Recommended fix High confidence

ruby-saml version 1.18.0 (or 1.12.4) / omniauth-saml version 2.2.3 (or 2.1.3 or 1.10.6)

  1. Identify the current version of ruby-saml or omniauth-saml in your project by checking your Gemfile or gem lock file
  2. Run 'gem list ruby-saml' or 'gem list omniauth-saml' to confirm the installed version
  3. For ruby-saml: Upgrade to version 1.12.4 or 1.18.0 (or latest 1.x stable) by running 'gem install ruby-saml -v 1.18.0' or updating your Gemfile with gem 'ruby-saml', '~> 1.18.0'
  4. For omniauth-saml: Upgrade to version 1.10.6, 2.1.3, or 2.2.3 (or latest stable) by updating your Gemfile with the appropriate version constraint
  5. Run 'bundle install' or 'bundle update ruby-saml' to apply the changes
  6. Run your test suite to verify the upgrade does not break existing functionality, particularly SAML authentication flows
  7. Deploy the updated gem version to your production environment
  8. Monitor authentication logs to confirm SAML single sign-on continues to work correctly after the upgrade
Caveat Review ruby-saml changelog for any breaking changes between your current version and 1.18.0; minor version upgrades typically have minimal breaking changes but custom XML parsing configurations may need adjustment

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25292 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data