Ruby SAML allows remote Denial of Service (DoS) with compressed SAML responsesGHSA-92rq-c8cf-prrq
HIGHFix: SAML-Toolkits/ruby-saml@acac9e9GHSA-92rq-c8cf-prrq is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in ruby-saml. A fix is available for ruby-saml — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-92rq-c8cf-prrq.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
ruby-saml💎ruby-samlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Prior to versions 1.12.4 and 1.18.0, ruby-saml is susceptible to remote Denial of Service (DoS) with compressed SAML responses. ruby-saml uses zlib to decompress SAML responses in case they're compressed. It is possible to bypass the message size check with a compressed assertion since the message size is checked before inflation and not after. This issue may lead to remote Denial of Service (DoS). Versions 1.12.4 and 1.18.0 fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | ruby-saml | all versions | 1.12.4bundle update ruby-saml --conservative |
| 💎RubyGems | ruby-saml | ≥ 1.13.0&&< 1.18.0 | 1.18.0bundle update ruby-saml --conservative |
Affected Products
omniauth samlomniauthruby-samloneloginDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ruby-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ruby-saml to 1.12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92rq-c8cf-prrq is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-92rq-c8cf-prrq in your dependencies?
Find it across RubyGems, including transitive dependencies.