CVE-2015-20108

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 39% of all CVEs by exploit prediction. 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: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

xml_security.rb in the ruby-saml gem before 1.0.0 for Ruby allows XPath injection and code execution because prepared statements are not used.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
67.8%
KEV
Not listed

Published

May 27, 2023

Last Modified

January 14, 2025

Advisory Details (4)

Auto-updated Jun 8, 2026
Patch available. Sources: github_commit, github_pr.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20230703-0003/
github_pr

Some features from the PR #197 (PR splitted)

Fix merged in SAML-Toolkits/ruby-saml PR #225 on 2015-04-29 — awaiting tagged release

https://github.com/SAML-Toolkits/ruby-saml/pull/225
generic

Comparing v0.9.2...v1.0.0 · SAML-Toolkits/ruby-saml · GitHub

https://github.com/SAML-Toolkits/ruby-saml/compare/v0.9.2...v1.0.0
github_commit Patch Available

commit 9853651b96b9 (SAML-Toolkits/ruby-saml)

Patch available: SAML-Toolkits/ruby-saml 1.4.1 (contains commit 9853651b96b9)

https://github.com/SAML-Toolkits/ruby-saml/commit/9853651b96b99653ea8627d757d46bfe62ab6448

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
ruby-saml0.0.5 ... 0.9.4 (53 versions)1.0.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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-11 08:23 UTCEPSS rescore
  2. 2026-07-09 19:05 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-07 13:42 UTCEPSS rescore
  5. 2026-07-06 16:24 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-05 02:26 UTCEPSS rescore
  8. 2026-07-04 06:27 UTCEPSS rescore
  9. 2026-07-02 15:21 UTCEPSS rescore
  10. 2026-07-01 15:02 UTCEPSS rescore
  11. 2026-07-01 15:02 UTCEPSS rescore
  12. 2026-06-30 23:19 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-29 14:03 UTCEPSS rescore
  15. 2026-06-28 14:03 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 20:04 UTCOSV refresh
  18. 2026-06-27 03:05 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-22 14:22 UTCEPSS rescore
Show 45 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-19 19:23 UTCEPSS rescore
  5. 2026-06-19 19:23 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-18 17:49 UTCEPSS rescore
  8. 2026-06-17 17:49 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-16 17:49 UTCEPSS rescore
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-14 23:14 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-11 13:57 UTCEPSS rescore
  16. 2026-06-10 22:15 UTCEPSS rescore
  17. 2026-06-10 06:47 UTCOSV refresh
  18. 2026-06-08 14:14 UTCEPSS rescore
  19. 2026-06-07 15:22 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-04 13:10 UTCEPSS rescore
  25. 2026-06-04 13:09 UTCEPSS rescore
  26. 2026-06-02 20:10 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 22:28 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-29 13:41 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-26 13:41 UTCEPSS rescore
  41. 2026-05-26 07:16 UTCEPSS rescore
  42. 2026-05-26 07:16 UTCEPSS rescore
  43. 2026-05-25 00:29 UTCEG score recompute
  44. 2026-05-24 16:43 UTCEPSS rescore
  45. 2026-05-23 15:10 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2015-20108?
CVE-2015-20108 is a critical vulnerability published on May 27, 2023. xml_security.rb in the ruby-saml gem before 1.0.0 for Ruby allows XPath injection and code execution because prepared statements are not used.
When was CVE-2015-20108 disclosed?
CVE-2015-20108 was first published in the National Vulnerability Database on May 27, 2023, with the most recent update on January 14, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-20108 actively exploited?
CVE-2015-20108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-20108?
CVE-2015-20108 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-20108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-20108, 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-2015-20108

Explore →

Is Your Infrastructure Affected by CVE-2015-20108?

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

Start Free Scan →Browse All CVEs