Is rubygems-update 2.7 vulnerable?

RubyGems · 12 releases from 2.7.0 to 2.7.11 · latest rubygems-update is 4.1.0 · checked 18 Nov 2026

No known advisories in the last release

rubygems-update 2.7.11, the last 2.7 release, has no known advisories. 13 advisories affect earlier 2.7.x releases, so update to 2.7.11.

Update within 2.7:bundle update --conservative rubygems-update # Gemfile: '>= 2.7.11'

Is your project on an affected rubygems-update?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.7.x, affecting earlier releases

  • MediumCVE-2018-1000079GHSA-8qxg-mff5-j3wc14 May 2022

    RubyGems Path Traversal vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • CriticalCVE-2018-1000076GHSA-mc6j-h948-v2p614 May 2022

    RubyGems Improper Verification of Cryptographic Signature vulnerability

    Affected
    >=2.2.0 <2.7.6
    Fixed in
    2.7.6
  • HighCVE-2018-1000074GHSA-qj2w-mw2r-pv3914 May 2022

    RubyGems Deserialization of Untrusted Data vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • MediumCVE-2018-1000078GHSA-87qx-g5wg-mwmj14 May 2022

    RubyGems Cross-site Scripting vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • MediumCVE-2018-1000077GHSA-gv86-43rv-79m214 May 2022

    RubyGems Improper Input Validation vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • HighCVE-2018-1000075GHSA-74pv-v9gh-h25p13 May 2022

    RubyGems Infinite Loop vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • HighCVE-2018-1000073GHSA-gx69-6cp4-hxrj13 May 2022

    RubyGems Link Following vulnerability

    Affected
    <2.7.6
    Fixed in
    2.7.6
  • HighCVE-2019-8325GHSA-4wm8-fjv7-j77420 Jun 2019

    RubyGems Escape sequence injection in errors

    Affected
    >=2.6.0 <2.7.9 · >=3.0.0 <3.0.2
    Fixed in
    2.7.9, 3.0.2
  • HighCVE-2019-8320GHSA-5x32-c9mf-49cc20 Jun 2019

    RubyGems Delete directory using symlink when decompressing tar

    Affected
    >=2.7.6 <2.7.9 · >=3.0.0 <3.0.3
    Fixed in
    2.7.9, 3.0.3
  • HighCVE-2019-8324GHSA-76wm-422q-92mq20 Jun 2019

    Code injection in RubyGems

    Affected
    >=2.6.0 <2.7.9 · >=3.0.0 <3.0.2
    Fixed in
    2.7.9, 3.0.2
  • HighCVE-2019-8321GHSA-fr32-gr5c-xq5c20 Jun 2019

    RubyGems Escape sequence injection vulnerability in verbose

    Affected
    >=2.6.0 <2.7.9 · >=3.0.0 <3.0.2
    Fixed in
    2.7.9, 3.0.2
  • HighCVE-2019-8322GHSA-mh37-8c3g-3fgc20 Jun 2019

    RubyGems Escape sequence injection vulnerability in gem owner

    Affected
    >=2.6.0 <2.7.9 · >=3.0.0 <3.0.2
    Fixed in
    2.7.9, 3.0.2
  • HighCVE-2019-8323GHSA-3h4r-pjv6-cph920 Jun 2019

    RubyGems Escape sequence injection vulnerability in api response handling

    Affected
    >=2.6.0 <2.7.9 · >=3.0.0 <3.0.2
    Fixed in
    2.7.9, 3.0.2

Every rubygems-update 2.7.x release

Affected: 2.7.0 to 2.7.8. 2.7.9 and later are not affected. Latest rubygems-update: 4.1.0.

VersionKnown advisories
rubygems-update 2.7.11None
rubygems-update 2.7.10None
rubygems-update 2.7.9None
rubygems-update 2.7.8CVE-2019-8325, CVE-2019-8320, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.7CVE-2019-8325, CVE-2019-8320, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.6CVE-2019-8325, CVE-2019-8320, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.5CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.4CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.3CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.2CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.1CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323
rubygems-update 2.7.0CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073, CVE-2019-8325, CVE-2019-8324, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323

Which of your client projects are still on rubygems-update 2.7?

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.