CVE-2017-0901

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 20.6%, top 4% 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
Weaponized
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 29%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

RubyGems version 2.6.12 and earlier fails to validate specification names, allowing a maliciously crafted gem to potentially overwrite any file on the filesystem.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
98.0%
KEV
Not listed

Published

August 31, 2017

Last Modified

May 13, 2026

References (30)

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturuby2.3-tcltk (2.3.1-2~16.04.10) @ xenial2026-05-22ubuntu
ubunturuby1.9.3 (1.9.3.484-2ubuntu1.5) @ trusty2026-05-22ubuntu
ubunturuby2.3 (2.3.3-1ubuntu1.3) @ artful2026-05-22ubuntu
redhatrh-ruby23-ruby-0:2.3.6-67.el72018-03-26redhat
redhatrh-ruby22-ruby-0:2.2.9-19.el72018-03-26redhat
redhatruby-0:2.0.0.648-33.el7_42018-02-28redhat
redhatrh-ruby24-ruby-0:2.4.2-86.el72017-12-19redhat

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
rubygems-update0.8.10 ... 2.6.9 (139 versions)2.6.13—

All Vendor Advisories

(7)

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-42611✓ verified
    First seen Sep 4, 2017

    RubyGems < 2.6.13 - Arbitrary File Overwrite

    Open source ↗

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2017-0901?
CVE-2017-0901 is a high vulnerability published on August 31, 2017. RubyGems version 2.6.12 and earlier fails to validate specification names, allowing a maliciously crafted gem to potentially overwrite any file on the filesystem.
When was CVE-2017-0901 disclosed?
CVE-2017-0901 was first published in the National Vulnerability Database on August 31, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0901 actively exploited?
CVE-2017-0901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0901?
CVE-2017-0901 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-0901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0901, 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-2017-0901

Explore →

Is Your Infrastructure Affected by CVE-2017-0901?

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

Start Free Scan →Browse All CVEs