cve.bz

CVE-2025-25291 Interpretation Conflict

9.3 criticalExploit referenceEPSS 34%Fix available

Critical (9.3). EPSS 34% estimated probability of exploitation activity in the next 30 days. Fixed in ruby-saml 1.12.4, 1.18.0.

On this page
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 fix the issue.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
34% (up from 21% a week ago; 21% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2025-04-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-347 Improper Verification of Cryptographic Signature
CWE-436 Interpretation Conflict
OWASP Top 10
A04:2025 Cryptographic Failures, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-25291 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-25291?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-25291?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-25291 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
omniauth:omniauth_samlbefore 1.10.6
omniauth:omniauth_samlfrom 2.0.0 before 2.1.3
omniauth:omniauth_samlfrom 2.2.0 before 2.2.3
onelogin:ruby-samlbefore 1.12.4
onelogin:ruby-samlfrom 1.13.0 before 1.18.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4vc4-m8qh-g8jmRubyGemsruby-saml<1.12.41.12.4
GHSA-4vc4-m8qh-g8jmRubyGemsruby-saml>=1.13.0 <1.18.01.18.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11ruby-saml1.11.0-1+deb11u2DLA-4115-1
Debian12ruby-samlno fix listedDEBIAN-CVE-2025-25291
UbuntuPro:16.04:LTSruby-samlno fix listedUBUNTU-CVE-2025-25291 USN-7409-1
UbuntuPro:18.04:LTSruby-saml1.7.2-1ubuntu0.1~esm2UBUNTU-CVE-2025-25291 USN-7409-1
UbuntuPro:20.04:LTSruby-saml1.11.0-1ubuntu0.1+esm1UBUNTU-CVE-2025-25291 USN-7409-1
UbuntuPro:22.04:LTSruby-saml1.13.0-1ubuntu0.1+esm1UBUNTU-CVE-2025-25291 USN-7409-1
UbuntuPro:24.04:LTSruby-saml1.15.0-1ubuntu0.24.04.1+esm1UBUNTU-CVE-2025-25291 USN-7409-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_SPECIFIC_APPS GitLab SAML Authentication Bypass (CVE-2025-25291) sid 2065765

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON