Answer in brief
CVE-2025-46551 records a Unknown severity vulnerability in JRuby-OpenSSL has hostname verification disabled by default. The current sources do not mark it as known exploited. The current feed maps org.jruby:jruby (maven), org.jruby:jruby (maven), rubygems:jruby-openssl (maven), jruby-openssl (rubygems). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.jruby:jruby (maven), org.jruby:jruby (maven), rubygems:jruby-openssl (maven), jruby-openssl (rubygems). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.jruby:jrubymaven | >=10.0.0.0 <10.0.0.1 | 10.0.0.1 |
| org.jruby:jrubymaven | >=9.3.4.0 <9.4.12.1 | 9.4.12.1 |
| rubygems:jruby-opensslmaven | >=0.12.1 <0.15.4 | 0.15.4 |
| jruby-opensslrubygems | >=0.12.1 <0.15.4 | 0.15.4 |
Published upstream
May 7, 2025
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
### Summary When verifying SSL certificates, jruby-openssl is not verifying that the hostname presented in the certificate matches the one we are trying to connect to, meaning a MITM could just present _any_ valid cert for a completely different domain they own, and JRuby wouldn't complain. ### Details n/a ### PoC An example domain bad.substitutealert.com was created to present the a certificate for the domain s8a.me. The following script run in IRB in CRuby 3.4.3 will fail with `certificate verify failed (hostname mismatch)`, but will work just fine in JRuby 10.0.0.0 and JRuby 9.4.2.0, both of which use jruby-openssl version 0.15.3 ```ruby require "net/http" require "openssl" uri = URI("https://bad.substitutealert.com/") https = Net::HTTP.new(uri.host, uri.port) https.use_ssl = true https.verify_mode = OpenSSL::SSL::VERIFY_PEER body = https.start { https.get(uri.request_uri).body } puts body ``` ### Impact Anybody using JRuby to make requests of external APIs, or scraping the web, that depends on https to connect securely
Quoted source text, attributed separately from HOL analysis.