CVE-2024-45409

CRITICALNVD 9.810.0
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-09-10. NVD baseline CVSS 9.8; sources differ by 0.2.

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

Also known asEUVD-2024-2828 (ENISA EUVD) · GHSA-jw9c-mfg7-9rx2 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 12%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <= 1.16.0 does not properly verify the signature of the SAML Response. An unauthenticated attacker with access to any signed saml document (by the IdP) can thus forge a SAML Response/Assertion with arbitrary contents. This would allow the attacker to log in as arbitrary user within the vulnerable system. This vulnerability is fixed in 1.17.0 and 1.12.3.

CVSS v3
9.8
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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
12%
EPSS %ILE
96th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
12% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (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

September 10, 2024

Last Modified

November 4, 2026

Advisory Details (7)

Auto-updated Nov 7, 2026
Patch available. Sources: github, github_commit.
Web page

Ruby-SAML pwned by XML signature wrapping attacks | Hacker News

https://news.ycombinator.com/item?id=41586031
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3949-1] ruby-saml security update

https://lists.debian.org/debian-lts-announce/2024/11/msg00006.html
GitHub advisoryMentions a patch (unverified)

Improper Verification of Cryptographic Signature in omniauth-saml · Advisory · omniauth/omniauth-saml · GitHub

Affected: v1.17.

https://github.com/omniauth/omniauth-saml/security/advisories/GHSA-cvp8-5r8g-fhvq
GitHub advisoryMentions a patch (unverified)

SAML authentication bypass via Incorrect XPath selector · Advisory · SAML-Toolkits/ruby-saml · GitHub

https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2
GitHub commit Patch Available

commit 4865d030cae9 (SAML-Toolkits/ruby-saml)

Patch available: SAML-Toolkits/ruby-saml v1.17.0 (contains commit 4865d030cae9)

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

commit 1ec5392bc506 (SAML-Toolkits/ruby-saml)

Patch available: SAML-Toolkits/ruby-saml v1.12.3 (contains commit 1ec5392bc506)

https://github.com/SAML-Toolkits/ruby-saml/commit/1ec5392bc506fe43a02dbb66b68741051c5ffeae

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturuby-saml (1.13.0-1ubuntu0.1) @ jammy2026-11-12ubuntu
rubygemsruby-saml @ 1.17.0 (fixes >= 1.13.0, < 1.17.0)—ghsa
rubygemsruby-saml @ 1.12.3 (fixes < 1.12.3)—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
  • every version up to 1.11.0-1+deb11u1: fixed in 1.11.0-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-saml1.13.0-1
  • every version up to 1.13.0-1+deb12u1: fixed in 1.13.0-1+deb12u1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-saml1.13.0, 1.14.0, 1.15.0, 1.16.0
  • every version up to 1.12.3: fixed in 1.12.3
  • 1.13.0 up to 1.17.0: fixed in 1.17.0
—

Weakness Classification(1)

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 15× in last 7d / 58× 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 255 rows on record for this CVE.

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. None are among the latest 100 rows. The 155 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCsynacktiv/CVE-2024-45409
    Published Oct 7, 2024

    Ruby-SAML / GitLab Authentication Bypass (CVE-2024-45409) exploit

    Open source ↗

Frequently asked(5)

What is CVE-2024-45409?
CVE-2024-45409 is a critical-severity vulnerability; its CVE record was published on September 10, 2024. The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <= 1.16.0 does not properly verify the signature of the SAML Response. An unauthenticated attacker with access to any signed saml document (by the IdP) can thus forge a SAML…
When was the CVE record for CVE-2024-45409 published?
The CVE record for CVE-2024-45409 was published on September 10, 2024. 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 4, 2026; the record at its source may have been updated since.
Is CVE-2024-45409 actively exploited?
CVE-2024-45409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45409?
CVE-2024-45409 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2024-45409?
A fix for CVE-2024-45409 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-45409 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-2024-45409

Explore →

Is Your Infrastructure Affected by CVE-2024-45409?

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