What is CVE-2024-45409?

CVE-2024-45409 is a critical-severity security vulnerability in ruby-saml (rubygems), affecting versions < 1.12.3. It is fixed in 1.12.3, 1.17.0.

How severe is CVE-2024-45409?

CVE-2024-45409 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ruby-saml are affected by CVE-2024-45409?

ruby-saml (rubygems) versions < 1.12.3 is affected.

Is there a fix for CVE-2024-45409?

Yes. CVE-2024-45409 is fixed in 1.12.3, 1.17.0. Upgrade to this version or later.

Is CVE-2024-45409 exploitable, and should I be worried?

Whether CVE-2024-45409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-45409 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-45409?

Upgrade: ruby-saml to 1.12.3 or later, ruby-saml to 1.17.0 or later.

CVE-2024-45409 in ruby-saml

Q: How severe is CVE-2024-45409?

CVE-2024-45409 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ruby-saml are affected by CVE-2024-45409?

ruby-saml (rubygems) versions < 1.12.3 is affected.

Q: Is there a fix for CVE-2024-45409?

Yes. CVE-2024-45409 is fixed in 1.12.3, 1.17.0. Upgrade to this version or later.

Q: Is CVE-2024-45409 exploitable, and should I be worried?

Whether CVE-2024-45409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-45409 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-45409?

Upgrade: ruby-saml to 1.12.3 or later, ruby-saml to 1.17.0 or later.

Summary

SAML authentication bypass via Incorrect XPath selector

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 was reported by ahacker1 of SecureSAML ([email protected])

Impact

CVE-2024-45409 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.12.3, 1.17.0); upgrading removes the vulnerable code path.

Affected versions

ruby-saml (< 1.12.3) ruby-saml (>= 1.13.0, < 1.17.0)

Security releases

ruby-saml → 1.12.3 (rubygems) ruby-saml → 1.17.0 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

ruby-saml to 1.12.3 or later; ruby-saml to 1.17.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-45409? CVE-2024-45409 is a critical-severity security vulnerability in ruby-saml (rubygems), affecting versions < 1.12.3. It is fixed in 1.12.3, 1.17.0.
How severe is CVE-2024-45409? CVE-2024-45409 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ruby-saml are affected by CVE-2024-45409? ruby-saml (rubygems) versions < 1.12.3 is affected.
Is there a fix for CVE-2024-45409? Yes. CVE-2024-45409 is fixed in 1.12.3, 1.17.0. Upgrade to this version or later.
Is CVE-2024-45409 exploitable, and should I be worried? Whether CVE-2024-45409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-45409 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-45409?
- Upgrade ruby-saml to 1.12.3 or later
- Upgrade ruby-saml to 1.17.0 or later

Other vulnerabilities in ruby-saml

CVE-IDSeverityPackage summary

CVE-2025-66568Criticalruby-saml: Ruby-saml allows a Libxml2 Canonicalization error to bypass Digest/Signature validation CVE-2025-66567Criticalruby-saml: Ruby-saml has a SAML authentication bypass due to namespace handling (parser differential)CVE-2025-54572Mediumruby-saml: Ruby SAML DOS vulnerability with large SAML response CVE-2025-25292Criticalruby-saml: Ruby SAML allows a SAML authentication bypass due to namespace handling (parser differential)CVE-2025-25291Criticalruby-saml: Ruby SAML allows a SAML authentication bypass due to DOCTYPE handling (parser differential)