CVE-2024-45409: ruby-saml · Improper Verification of Cryptographic Signature
Affects ruby-samlSource CVE Database V5
Public exploit available · 10% EPSS · CVSS 10.0 Critical : upgrade to 1.17.0 or 1.12.3 as a priority.
Data as of 4 Nov 2026, 00:28 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 10.0 |
|---|
- EPSS
- 10.6% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- Proof of concept is public or traded
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2024-10-16.
- Patch
- Available – fixed in 1.17.0, 1.12.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 10 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 13 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 36 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade ruby-saml to 1.17.0 or 1.12.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAML-Toolkitsruby-saml | Affected
| Fixed in
|
| SAML-Toolkitsruby-saml | Affected
| Fixed in
|
AI-suggested
Upgrade ruby-saml to version 1.12.3 or later if using a version <= 1.12.2, or to version 1.17.0 or later if using versions between 1.13.0 and 1.16.0. These versions contain the official fixes for the signature verification flaw. No other mitigations are indicated by the vendor advisory.
Description
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.
References
- github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2 (opens in a new tab)
- github.com/omniauth/omniauth-saml/security/advisories/GHSA-cvp8-5r8g-fhvq (opens in a new tab)
- github.com/SAML-Toolkits/ruby-saml/commit/1ec5392bc506fe43a02dbb66b68741051c5ffeae (opens in a new tab)
- github.com/SAML-Toolkits/ruby-saml/commit/4865d030cae9705ee5cdb12415c654c634093ae7 (opens in a new tab)
- ssoready.com/blog/engineering/ruby-saml-pwned-by-xml-signature-wrapping-attacks/ (opens in a new tab)
- news.ycombinator.com/item?id=41586031 (opens in a new tab)
- security.netapp.com/advisory/ntap-20240926-0008/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/11/msg00006.html (opens in a new tab)