Is rubygems-update 2.1 vulnerable?
RubyGems · 12 releases from 2.1.0 to 2.1.11 · latest rubygems-update is 4.1.0 · checked 18 Nov 2026
Yes: 12 known advisories
Yes. rubygems-update 2.1.11, the last 2.1 release, is affected by 12 known security advisories (2 critical, 6 high, 4 medium), including CVE-2017-0903, CVE-2017-0899, CVE-2017-0900. 1 more affects earlier 2.1.x releases. Upgrade to 2.7.6 or later to fix all of them.
bundle update --conservative rubygems-update # Gemfile: '>= 2.7.6'Is your project on an affected rubygems-update?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting rubygems-update 2.1.11
RubyGems Improper Input Validation vulnerability
- Affected
- <2.0.17 · >=2.1.0.rc.1 <2.2.5 · >=2.3.0 <2.4.8
- Fixed in
- 2.0.17, 2.2.5, 2.4.8
RubyGems Path Traversal vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
RubyGems Improper Input Validation vulnerability
- Affected
- <2.6.13
- Fixed in
- 2.6.13
RubyGems Deserialization of Untrusted Data vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
RubyGems Cross-site Scripting vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
RubyGems Improper Input Validation vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
RubyGems Infinite Loop vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
RubyGems vulnerable to Deserialization of Untrusted Data
- Affected
- >=2.0.0 <2.6.14
- Fixed in
- 2.6.14
RubyGems may allow a maliciously crafted gem to overwrite files
- Affected
- <2.6.13
- Fixed in
- 2.6.13
RubyGems Code Injection vulnerability
- Affected
- <2.6.13
- Fixed in
- 2.6.13
RubyGems has Origin Validation Error vulnerability
- Affected
- <2.6.13
- Fixed in
- 2.6.13
RubyGems Link Following vulnerability
- Affected
- <2.7.6
- Fixed in
- 2.7.6
Fixed within 2.1.x, affecting earlier releases
RubyGems Regular Expression Denial of Service
- Affected
- <1.8.23.2 · >=1.8.24 <1.8.27 · >=2.0.0 <2.0.10 · >=2.1.0 <2.1.5
- Fixed in
- 1.8.23.2, 1.8.27, 2.0.10, 2.1.5
Every rubygems-update 2.1.x release
Affected: 2.1.0 to 2.1.11. Latest rubygems-update: 4.1.0.
| Version | Known advisories |
|---|---|
| rubygems-update 2.1.11 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.10 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.9 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.8 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.7 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.6 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.5 | CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.4 | CVE-2013-4363, CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.3 | CVE-2013-4363, CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.2 | CVE-2013-4363, CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.1 | CVE-2013-4363, CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
| rubygems-update 2.1.0 | CVE-2013-4363, CVE-2015-4020, CVE-2018-1000079, CVE-2017-0900, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2017-0903, CVE-2017-0901, CVE-2017-0899, CVE-2017-0902, CVE-2018-1000073 |
Which of your client projects are still on rubygems-update 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact rubygems-update version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other rubygems-update versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.