Is org.jruby:jruby-stdlib 9.1 vulnerable?

Maven · 18 releases from 9.1.0 to 9.1.17 · latest org.jruby:jruby-stdlib is 10.1.3.0 · checked 18 Nov 2026

No known advisories in the last release

org.jruby:jruby-stdlib 9.1.17, the last 9.1 release, has no known advisories. 7 advisories affect earlier 9.1.x releases, so update to 9.1.17.

Update within 9.1:mvn versions:use-dep-version -Dincludes=org.jruby:jruby-stdlib -DdepVersion=9.1.17 -DforceVersion=true

Is your project on an affected org.jruby:jruby-stdlib?

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

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

Fixed within 9.1.x, affecting earlier releases

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

    RubyGems Path Traversal vulnerability

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

    RubyGems Improper Verification of Cryptographic Signature vulnerability

    Affected
    <9.1.16.0
    Fixed in
    9.1.16.0
  • HighCVE-2018-1000074GHSA-qj2w-mw2r-pv3914 May 2022

    RubyGems Deserialization of Untrusted Data vulnerability

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

    RubyGems Cross-site Scripting vulnerability

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

    RubyGems Improper Input Validation vulnerability

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

    RubyGems Infinite Loop vulnerability

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

    RubyGems Link Following vulnerability

    Affected
    <9.1.16.0
    Fixed in
    9.1.16.0

Every org.jruby:jruby-stdlib 9.1.x release

Affected: 9.1.0 to 9.1.15. 9.1.16 and later are not affected. Latest org.jruby:jruby-stdlib: 10.1.3.0.

VersionKnown advisories
org.jruby:jruby-stdlib 9.1.17None
org.jruby:jruby-stdlib 9.1.16None
org.jruby:jruby-stdlib 9.1.15CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.14CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.13CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.12CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.11CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.10CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.9CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.8CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.7CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.6CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.5CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.4CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.3CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.2CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.1CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073
org.jruby:jruby-stdlib 9.1.0CVE-2018-1000079, CVE-2018-1000076, CVE-2018-1000074, CVE-2018-1000078, CVE-2018-1000077, CVE-2018-1000075, CVE-2018-1000073

Which of your client projects are still on org.jruby:jruby-stdlib 9.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.jruby:jruby-stdlib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.jruby:jruby-stdlib versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.