CVE-2024-45409

CRITICALNVD 10.010.0
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Elevated
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 11%CVSS: 10.0Exploit: NoneExposed: 0

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
10.0
EG Score
10.0(low)
EPSS
95.3%
KEV
Not listed

Published

September 10, 2024

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Jul 4, 2026
Patch available. Sources: github_commit, github.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20240926-0008/
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2024/11/msg00006.html
github Patch Available

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 Patch Available

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
generic🔴 Active Exploitation

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

https://news.ycombinator.com/item?id=41586031

Vendor Advisories for CVE-2024-45409(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturuby-saml (1.1.2-1ubuntu1+esm1) @ xenial2026-05-23ubuntu

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

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
ruby-saml1.13.0, 1.14.0, 1.15.0, 1.16.01.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 5× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:26 UTCEPSS rescore
  2. 2026-07-04 06:30 UTCEPSS rescore
  3. 2026-07-01 15:05 UTCEPSS rescore
  4. 2026-06-30 23:21 UTCEPSS rescore
  5. 2026-06-30 23:21 UTCEPSS rescore
  6. 2026-06-29 14:05 UTCEPSS rescore
  7. 2026-06-28 04:55 UTCEPSS rescore
  8. 2026-06-28 04:55 UTCEPSS rescore
  9. 2026-06-27 03:07 UTCEPSS rescore
  10. 2026-06-27 03:07 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 22:31 UTCOSV refresh
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 17:52 UTCEPSS rescore
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
Show 32 more
  1. 2026-06-15 17:47 UTCEPSS rescore
  2. 2026-06-12 23:11 UTCEPSS rescore
  3. 2026-06-12 23:11 UTCEPSS rescore
  4. 2026-06-11 13:59 UTCEPSS rescore
  5. 2026-06-10 22:18 UTCEPSS rescore
  6. 2026-06-10 13:21 UTCEPSS rescore
  7. 2026-06-08 14:16 UTCEPSS rescore
  8. 2026-06-08 14:16 UTCEPSS rescore
  9. 2026-06-07 21:46 UTCOSV refresh
  10. 2026-06-06 13:46 UTCEPSS rescore
  11. 2026-06-06 13:46 UTCEPSS rescore
  12. 2026-06-05 22:46 UTCEPSS rescore
  13. 2026-06-05 22:46 UTCEPSS rescore
  14. 2026-06-05 06:09 UTCEPSS rescore
  15. 2026-06-05 06:09 UTCEPSS rescore
  16. 2026-06-04 13:11 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-02 20:12 UTCEPSS rescore
  19. 2026-06-02 20:12 UTCEPSS rescore
  20. 2026-06-01 13:51 UTCEPSS rescore
  21. 2026-06-01 13:51 UTCEPSS rescore
  22. 2026-05-31 22:30 UTCEPSS rescore
  23. 2026-05-31 22:30 UTCEPSS rescore
  24. 2026-05-31 00:16 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-29 13:43 UTCEPSS rescore
  27. 2026-05-28 13:44 UTCEPSS rescore
  28. 2026-05-28 13:44 UTCEPSS rescore
  29. 2026-05-27 13:40 UTCEPSS rescore
  30. 2026-05-27 13:40 UTCEPSS rescore
  31. 2026-05-23 11:08 UTCEG score recompute
  32. 2026-05-23 11:08 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsynacktiv/CVE-2024-45409
    First seen Oct 7, 2024

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

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-45409?
CVE-2024-45409 is a critical vulnerability 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 CVE-2024-45409 disclosed?
CVE-2024-45409 was first published in the National Vulnerability Database on September 10, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-45409 actively exploited?
CVE-2024-45409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-45409?
CVE-2024-45409 has a CVSS v3 base score of 10.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2024-45409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-45409, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs