Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-25292: Ruby SAML vulnerable to SAML authentication bypass due to namespace handling (parser differential)

CriticalCVSS 9.3 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 57/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 65% (FIRST EPSS); higher than 99.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: ruby-saml (Debian:11) 1.11.0-1+deb11u2; omniauth-saml (RubyGems) 2.1.3, 2.2.3, 1.10.6; ruby-saml (RubyGems) 1.18.0, 1.12.4.

Add it to your regular patch cycle. Upgrade to ruby-saml (Debian:11) 1.11.0-1+deb11u2; omniauth-saml (RubyGems) 2.1.3, 2.2.3, 1.10.6; ruby-saml (RubyGems) 1.18.0, 1.12.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Mar 12, 2025
Updated
Jun 17, 2026
EPSS
65.0% · 99th percentile

Report tools

JSON

Action score

57

Plan

Add it to your regular patch cycle.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
20 / 30 · 65.0%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.3
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-25292

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for omniauth records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
omniauthomniauth saml
oneloginruby-saml
netappstoragegrid

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
Affected versions · NVD (6)

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

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11ruby-samlbefore 1.11.0-1+deb11u21.11.0-1+deb11u2
Debian:12ruby-samlfrom 0—
RubyGemsomniauth-samlfrom 2.0.0 · before 2.1.32.1.3
RubyGemsomniauth-samlfrom 2.2.0 · before 2.2.32.2.3
RubyGemsomniauth-samlbefore 1.10.61.10.6
RubyGemsruby-samlfrom 1.13.0 · before 1.18.01.18.0
RubyGemsruby-samlbefore 1.12.41.12.4

Same product

omniauth: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-25291ruby-saml vulnerable to SAML authentication bypass due to DOCTYPE handling (parser differential)
    43Plan
  • 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

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-saml1.11.0-1+deb11u2 · Debian:11Package registry (OSV)
RubyGems:omniauth-saml1.10.6Package registry (OSV)
RubyGems:omniauth-saml2.1.3Package registry (OSV)
RubyGems:omniauth-saml2.2.3Package registry (OSV)
RubyGems:ruby-saml1.12.4Package registry (OSV)
RubyGems:ruby-saml1.18.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

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

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-252910 days apartruby-saml vulnerable to SAML authentication bypass due to DOCTYPE handling (parser differential)
    43Plan

Not on record for this CVE: researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

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.

The bug in code

The whole CWE-347 class

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

Vulnerable

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

Fixed

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

Attack context

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

ATT&CK techniques

—

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records