Skip to content
Fencer Vulns
low 3.7

CVE-2025-46551 json

JRuby-OpenSSL has hostname verification disabled by default

published 2025-05-07 18 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-13880 , GHSA-72qj-48g4-5xgx

cvss
3.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

JRuby-OpenSSL is an add-on gem for JRuby that emulates the Ruby OpenSSL native library. Starting in JRuby-OpenSSL version 0.12.1 and prior to version 0.15.4 (corresponding to JRuby versions starting in 9.3.4.0 prior to 9.4.12.1 and 10.0.0.0 prior to 10.0.0.1), when verifying SSL certificates, JRuby-OpenSSL does not verify that the hostname presented in the certificate matches the one the user tries to connect to. This means a man-in-the-middle could just present any valid cert for a completely different domain they own, and JRuby would accept the cert. Anybody using JRuby to make requests of external APIs, or scraping the web, that depends on https to connect securely. JRuby-OpenSSL version 0.15.4 contains a fix for the issue. This fix is included in JRuby versions 10.0.0.1 and 9.4.12.1.

Patch / fix

  • maven rubygems:jruby-openssl 0.15.4
  • maven org.jruby:jruby 9.4.12.1, 10.0.0.1
  • rubygems jruby-openssl 0.15.4
  • jruby jruby-openssl 0.15.4
  • rubygems jruby-openssl 0.15.4
  • jruby jruby 9.4.12.1, 10.0.0.1
  • org.jruby jruby 9.4.12.1, 10.0.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-46551 updated cvss 6.5

jruby-openssl: jruby: JRuby-OpenSSL has hostname verification disabled by default

  • Red Hat AMQ Broker 7 jruby Red Hat build of Apache Camel for Spring Boot 4 jruby Red Hat Data Grid 8 jruby
    affected: no fix available “Fix deferred”
  • Red Hat Fuse 7 jruby, jruby-core
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Enterprise Application Platform 8 jruby Red Hat JBoss Enterprise Application Platform Expansion Pack jruby Red Hat Satellite 6 puppetserver
    affected: no fix available “Fix deferred”
  • Red Hat build of OptaPlanner 8 jruby, jruby-core Red Hat build of Quarkus jruby, jruby-core Red Hat Integration Camel K 1 jruby, jruby-core Red Hat JBoss Enterprise Application Platform 7 jruby, jruby-core Red Hat JBoss Enterprise Application Platform 8 jruby-core Red Hat JBoss Enterprise Application Platform Expansion Pack jruby-core
    +2 more products
    Red Hat Process Automation 7 jruby, jruby-core Red Hat streams for Apache Kafka jruby, jruby-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/jruby/jruby-openssl/security/advisories/GHSA-72qj-48g4-5xgx referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 5.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
CNA 4.0 5.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven rubygems:jruby-openssl
>=0.12.1, <0.15.4
0.15.4
maven org.jruby:jruby
>=10.0.0.0, <10.0.0.1
>=9.3.4.0, <9.4.12.1
10.0.0.1
9.4.12.1
rubygems jruby-openssl
>=0.12.1, <0.15.4
0.15.4

Affected products

  • jruby jruby-openssl

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-297 Improper Validation of Certificate with Host Mismatch

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.