CVE-2025-25292

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-03-12. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2025-6414 (ENISA EUVD) · GHSA-754f-8gm6-c4r2 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS PROB: 65%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
65%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
65% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 12, 2025

Last Modified

November 3, 2025

Advisory Details (10)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisory

GHSL-2024-329_GHSL-2024-330: Authentication bypasses in ruby-saml - CVE-2025-25291, CVE-2025-25292 | GitHub Security Lab

https://securitylab.github.com/advisories/GHSL-2024-329_GHSL-2024-330_ruby-saml
Web pageMentions a patch (unverified)

SAML roulette: the hacker always wins | PortSwigger Research

https://portswigger.net/research/saml-roulette-the-hacker-always-wins
GitHub advisoryMentions a patch (unverified)

Signature Wrapping Attack issue on ruby-saml · Advisory · omniauth/omniauth-saml · GitHub

https://github.com/omniauth/omniauth-saml/security/advisories/GHSA-hw46-3hmr-x9xv
GitHub advisoryMentions a patch (unverified)

SAML authentication bypass due to namespace handling (parser differential) · Advisory · SAML-Toolkits/ruby-saml · GitHub

https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-754f-8gm6-c4r2
GitHub release Patch Available

1.18.0 (Mar 12, 2025)

Patch available: SAML-Toolkits/ruby-saml v1.18.0

https://github.com/SAML-Toolkits/ruby-saml/releases/tag/v1.18.0
GitHub release Patch Available

1.12.4 (Mar 12, 2025)

Patch available: SAML-Toolkits/ruby-saml v1.12.4

https://github.com/SAML-Toolkits/ruby-saml/releases/tag/v1.12.4
GitHub commit Patch Available

commit e9c1cdbd0f9a (SAML-Toolkits/ruby-saml)

Patch available: SAML-Toolkits/ruby-saml v1.18.0 (contains commit e9c1cdbd0f9a)

https://github.com/SAML-Toolkits/ruby-saml/commit/e9c1cdbd0f9afa467b585de279db0cbd0fb8ae97
GitHub commit Patch Available

commit e76c5b36bac4 (SAML-Toolkits/ruby-saml)

Patch available: SAML-Toolkits/ruby-saml v1.12.4 (contains commit e76c5b36bac4)

https://github.com/SAML-Toolkits/ruby-saml/commit/e76c5b36bac40aedbf1ba7ffaaf495be63328cd9
Web page

Sign in as anyone: Bypassing SAML SSO authentication with parser differentials - The GitHub Blog

https://github.blog/security/sign-in-as-anyone-bypassing-saml-sso-authentication-with-parser-differentials
Web page

GitLab Critical Patch Release: 17.9.2, 17.8.5, 17.7.7 | GitLab Docs

https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released

Vendor Advisories for CVE-2025-25292(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturuby-saml (1.13.0-1ubuntu0.1+esm1) @ jammy2026-11-13ubuntu
rubygemsruby-saml @ 1.12.4 (fixes < 1.12.4)—ghsa
rubygemsruby-saml @ 1.18.0 (fixes >= 1.13.0, < 1.18.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-saml1.11.0-1, 1.11.0-1+deb11u1
  • every version up to 1.11.0-1+deb11u2: fixed in 1.11.0-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-saml1.13.0-1, 1.13.0-1+deb12u1, 1.15.0-1, 1.17.0-1
  • every version on: no fix on record
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-saml0.0.5 ... 1.9.0 (81 versions)
  • 1.13.0 up to 1.18.0: fixed in 1.18.0
  • every version up to 1.12.4: fixed in 1.12.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 210 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 21:23 UTCEchelonGraph re-scored
  2. 2026-11-13 21:23 UTCVendor advisory
  3. 2026-11-13 21:23 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-13 16:49 UTCEPSS rescoreEPSS 65% · 99th percentile
  5. 2026-11-12 20:36 UTCEchelonGraph re-scored
  6. 2026-11-12 20:36 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-11 20:51 UTCEchelonGraph re-scored
  8. 2026-11-11 20:51 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-11 16:36 UTCEPSS rescoreEPSS 65% · 99th percentile
  10. 2026-11-10 20:59 UTCEchelonGraph re-scored
  11. 2026-11-10 20:59 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-10 16:40 UTCEPSS rescoreEPSS 65% · 99th percentile
  13. 2026-11-09 20:57 UTCEchelonGraph re-scored
  14. 2026-11-09 20:56 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-09 16:32 UTCEPSS rescoreEPSS 65% · 99th percentile
  16. 2026-11-08 21:12 UTCEchelonGraph re-scored
  17. 2026-11-08 21:12 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-07 21:27 UTCEchelonGraph re-scored
  19. 2026-11-07 21:27 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-06 21:43 UTCEchelonGraph re-scored
  21. 2026-11-06 21:43 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-06 16:33 UTCEPSS rescoreEPSS 65% · 99th percentile
  23. 2026-11-05 21:59 UTCEchelonGraph re-scored
  24. 2026-11-05 21:59 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-11-05 16:35 UTCEPSS rescoreEPSS 65% · 99th percentile
Show 74 more
  1. 2026-11-05 10:25 UTCOSV refresh
  2. 2026-11-04 22:14 UTCEchelonGraph re-scored
  3. 2026-11-04 22:14 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-04 16:33 UTCEPSS rescoreEPSS 65% · 99th percentile
  5. 2026-11-03 22:24 UTCEchelonGraph re-scored
  6. 2026-11-03 22:24 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-03 16:44 UTCEPSS rescoreEPSS 65% · 99th percentile
  8. 2026-11-02 22:36 UTCEchelonGraph re-scored
  9. 2026-11-02 22:36 UTCVendor advisory
  10. 2026-11-02 22:36 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-01 22:38 UTCEchelonGraph re-scored
  12. 2026-11-01 22:38 UTCVendor advisory
  13. 2026-11-01 22:38 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-01 16:32 UTCEPSS rescoreEPSS 65% · 99th percentile
  15. 2026-11-01 08:08 UTCGHSA enrichmentGHSA-754f-8gm6-c4r2 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-01 08:08 UTCEchelonGraph re-scored
  17. 2026-10-31 22:54 UTCEchelonGraph re-scored
  18. 2026-10-31 22:54 UTCVendor advisory
  19. 2026-10-30 23:10 UTCEchelonGraph re-scored
  20. 2026-10-30 16:32 UTCEPSS rescoreEPSS 65% · 99th percentile
  21. 2026-10-29 23:26 UTCEchelonGraph re-scored
  22. 2026-10-29 23:26 UTCVendor advisory
  23. 2026-10-28 23:42 UTCEchelonGraph re-scored
  24. 2026-10-28 23:42 UTCVendor advisory
  25. 2026-10-28 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
  26. 2026-10-27 23:58 UTCEchelonGraph re-scored
  27. 2026-10-27 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
  28. 2026-10-27 00:11 UTCEchelonGraph re-scored
  29. 2026-10-26 16:29 UTCEPSS rescoreEPSS 65% · 99th percentile
  30. 2026-10-25 20:50 UTCVendor advisory
  31. 2026-10-25 16:39 UTCEchelonGraph re-scored
  32. 2026-10-25 16:31 UTCEPSS rescoreEPSS 65% · 99th percentile
  33. 2026-10-24 21:06 UTCEchelonGraph re-scored
  34. 2026-10-24 21:06 UTCVendor advisory
  35. 2026-10-23 21:22 UTCEchelonGraph re-scored
  36. 2026-10-23 21:22 UTCVendor advisory
  37. 2026-10-23 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
  38. 2026-10-22 21:37 UTCEchelonGraph re-scored
  39. 2026-10-22 21:37 UTCVendor advisory
  40. 2026-10-21 21:52 UTCEchelonGraph re-scored
  41. 2026-10-21 21:52 UTCVendor advisory
  42. 2026-10-21 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
  43. 2026-10-20 21:54 UTCEchelonGraph re-scored
  44. 2026-10-20 21:54 UTCVendor advisory
  45. 2026-10-20 16:31 UTCEPSS rescoreEPSS 65% · 99th percentile
  46. 2026-10-19 22:09 UTCEchelonGraph re-scored
  47. 2026-10-19 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
  48. 2026-10-18 20:56 UTCEchelonGraph re-scored
  49. 2026-10-18 05:43 UTCEchelonGraph re-scored
  50. 2026-10-17 21:07 UTCEchelonGraph re-scored
  51. 2026-10-16 21:22 UTCEchelonGraph re-scored
  52. 2026-10-16 16:38 UTCEPSS rescoreEPSS 65% · 99th percentile
  53. 2026-10-15 18:19 UTCEchelonGraph re-scored
  54. 2026-10-15 18:19 UTCVendor advisory
  55. 2026-10-14 16:31 UTCEPSS rescoreEPSS 65% · 99th percentile
  56. 2026-10-14 12:03 UTCEchelonGraph re-scored
  57. 2026-10-14 12:03 UTCVendor advisory
  58. 2026-10-13 16:32 UTCEPSS rescoreEPSS 65% · 99th percentile
  59. 2026-10-12 17:16 UTCEchelonGraph re-scored
  60. 2026-10-12 11:56 UTCVendor advisory
  61. 2026-10-11 20:48 UTCEchelonGraph re-scored
  62. 2026-10-11 18:58 UTCEchelonGraph re-scored
  63. 2026-10-11 15:36 UTCEchelonGraph re-scored
  64. 2026-10-11 13:47 UTCEPSS rescoreEPSS 65% · 99th percentile
  65. 2026-10-10 19:59 UTCEPSS rescoreEPSS 65% · 99th percentile
  66. 2026-10-09 20:06 UTCEPSS rescoreEPSS 65% · 99th percentile
  67. 2026-10-07 23:46 UTCEPSS rescoreEPSS 65% · 99th percentile
  68. 2026-10-06 15:16 UTCEPSS rescoreEPSS 65% · 99th percentile
  69. 2026-10-03 14:24 UTCEPSS rescoreEPSS 65% · 99th percentile
  70. 2026-10-02 20:40 UTCOSV refresh
  71. 2026-10-01 19:48 UTCEPSS rescoreEPSS 65% · 99th percentile
  72. 2026-09-30 15:02 UTCEPSS rescoreEPSS 65% · 99th percentile
  73. 2026-09-28 13:50 UTCEPSS rescoreEPSS 65% · 99th percentile
  74. 2026-09-26 15:58 UTCEPSS rescoreEPSS 65% · 99th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-25292?
CVE-2025-25292 is a critical-severity vulnerability; its CVE record was published on March 12, 2025. 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…
When was the CVE record for CVE-2025-25292 published?
The CVE record for CVE-2025-25292 was published on March 12, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-25292 actively exploited?
CVE-2025-25292 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 65% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-25292?
CVE-2025-25292 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-25292?
A fix for CVE-2025-25292 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-25292 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-25292

Explore →

Is Your Infrastructure Affected by CVE-2025-25292?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs