# JRuby-OpenSSL has hostname verification disabled by default Advisory record · `GHSA-72qj-48g4-5xgx` - **Identifiers:** `GHSA-72qj-48g4-5xgx` · `CVE-2025-46551` - **State:** Confirmed - **Severity:** CVSS 5.7 Medium - **Critical:** No - **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-297](https://cwe.mitre.org/data/definitions/297.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 7 May 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 May 2025, 17:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `rubygems:jruby-openssl` (Maven): affected `>=0.12.1, <0.15.4`; fixed in `0.15.4` - `org.jruby:jruby` (Maven): affected `>=10.0.0.0, <10.0.0.1 || >=9.3.4.0, <9.4.12.1`; fixed in `10.0.0.1`, `9.4.12.1` - `jruby-openssl` (RubyGems): affected `>=0.12.1, <0.15.4`; fixed in `0.15.4` ## 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. Written 2 Nov 2026. ## 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 - 5.7 Medium, CVSS 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`, from 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](https://osv.dev/vulnerability/GHSA-72qj-48g4-5xgx) ## Sources - [GitHub Advisory Database: GHSA-72qj-48g4-5xgx](https://github.com/advisories/GHSA-72qj-48g4-5xgx) - [OSV: GHSA-72qj-48g4-5xgx](https://osv.dev/vulnerability/GHSA-72qj-48g4-5xgx) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .