Is jruby-openssl 0.12 vulnerable?

RubyGems · 2 releases from 0.12.1 to 0.12.2 · latest jruby-openssl is 0.19.5 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. jruby-openssl 0.12.2, the last 0.12 release, is affected by 1 known security advisory (1 medium), including CVE-2025-46551. Upgrade to 0.15.4 or later to fix all of them.

Upgrade with:bundle update --conservative jruby-openssl # Gemfile: '>= 0.15.4'

Is your project on an affected jruby-openssl?

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

Advisories affecting jruby-openssl 0.12.2

  • MediumCVE-2025-46551GHSA-72qj-48g4-5xgx7 May 2025

    JRuby-OpenSSL has hostname verification disabled by default

    Affected
    >=0.12.1 <0.15.4
    Fixed in
    0.15.4

Every jruby-openssl 0.12.x release

Affected: 0.12.1 to 0.12.2. Latest jruby-openssl: 0.19.5.

VersionKnown advisories
jruby-openssl 0.12.2CVE-2025-46551
jruby-openssl 0.12.1CVE-2025-46551

Which of your client projects are still on jruby-openssl 0.12?

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

Other jruby-openssl 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.