Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The jruby-openssl package (RubyGems, and as a Maven artifact) versions 0.12.1 up to but not including 0.15.4 do not check that a server's certificate hostname matches the host being connected to, so SSL connections accept any valid certificate. An attacker able to intercept network traffic (a man-in-the-middle) could present a valid certificate for a different domain and the connection would succeed. Upgrade jruby-openssl to 0.15.4, and upgrade org.jruby:jruby to 10.0.0.1 or 9.4.12.1, which include the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.7 | Medium | 4.0 | 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 (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0020, the 9th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:17 UTC First seen by agentprime
- 31 Oct 2026, 14:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-72qj-48g4-5xgx
- OSV: GHSA-72qj-48g4-5xgx
- github.com/jruby/jruby-openssl/security/advisories/GHSA-72qj-48g4-5xgx
- nvd.nist.gov/vuln/detail/CVE-2025-46551
- github.com/jruby/jruby-openssl/commit/31a56d690ce9b8af47af09aaaf809081949ed285
- github.com/jruby/jruby-openssl/commit/b1fc5d645c0d90891b8865925ac1c15e3f15a055
- github.com/jruby/jruby-openssl
- github.com/rubysec/ruby-advisory-db/blob/master/gems/jruby-openssl/CVE-2025-46551.yml