Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-46551 — jruby

🟢 CVSS 3.7 — Low ⚠️ Exploit Public CWE-295 NVD
3.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

JRuby-OpenSSL has hostname verification disabled by default

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

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2025-46551 is classified as CWE-295: Improper Certificate Validation. A TLS certificate is accepted without proper verification, so a man-in-the-middle can present their own.

Affected software

CVE-2025-46551 is recorded against 4 packages.

  • jruby
  • jruby-openssl (from 0.12.1 up to 0.15.4)
  • org.jruby:jruby (from 9.3.4.0 up to 9.4.12.1)
  • rubygems:jruby-openssl (from 0.12.1 up to 0.15.4)

Timeline and source

Published on 7 May 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com
github.com
github.com

Other advisories for this package

jruby has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-295: Improper Certificate Validation) in other software:

CVE-2025-46551 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity LOW
CVSS Score 3.7
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CWE CWE-295
Public Exploit ⚠️ Yes
Source NVD
Published 2025-05-07
Updated 2026-08-20
Modified 2026-06-17

Affected Packages

Software From version Fixed in
jruby — —
jruby-openssl 0.12.1 0.15.4
org.jruby:jruby 9.3.4.0 9.4.12.1
rubygems:jruby-openssl 0.12.1 0.15.4

Exploit Protection

Are you running jruby?

CVE-2025-46551 carries CVSS 3.7 Low rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2025-46551 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓