How severe is GHSA-72qj-48g4-5xgx?

No CVSS score has been assigned to GHSA-72qj-48g4-5xgx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-72qj-48g4-5xgx?

GHSA-72qj-48g4-5xgx affects the following packages: rubygems:jruby-openssl (Maven), org.jruby:jruby (Maven), org.jruby:jruby (Maven), jruby-openssl (RubyGems). Ecosystems affected: Maven, RubyGems.

How do I fix GHSA-72qj-48g4-5xgx?

Update rubygems:jruby-openssl to 0.15.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72qj-48g4-5xgx is resolved across your whole dependency graph.

How do I detect GHSA-72qj-48g4-5xgx in my Maven, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rubygems:jruby-openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-72qj-48g4-5xgx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-72qj-48g4-5xgx actively exploited in the wild?

No public exploit code has been indexed for GHSA-72qj-48g4-5xgx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-72qj-48g4-5xgx?

GHSA-72qj-48g4-5xgx has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-72qj-48g4-5xgx?

GHSA-72qj-48g4-5xgx is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-72qj-48g4-5xgx published, and has it been updated?

GHSA-72qj-48g4-5xgx was published on May 7, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven💎 RubyGems

Not in CISA KEV

GHSA-72qj-48g4-5xgx — jruby-openssl

Fix: jruby/jruby-openssl@31a56d6

GHSA-72qj-48g4-5xgx is a CWE-295 vulnerability in rubygems:jruby-openssl. A fix is available for rubygems:jruby-openssl — see the affected versions and patch details below.

JRuby-OpenSSL has hostname verification disabled by default

Also known asCVE-2025-46551

Published

May 7, 2025

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-72qj-48g4-5xgx.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

☕rubygems:jruby-openssl☕org.jruby:jruby☕org.jruby:jruby💎jruby-openssl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`rubygems:jruby-openssl`	≥ 0.12.1&&< 0.15.4	0.15.4`rubygems:jruby-openssl:0.15.4`
☕Maven	`org.jruby:jruby`	≥ 10.0.0.0&&< 10.0.0.1	10.0.0.1`org.jruby:jruby:10.0.0.1`
☕Maven	`org.jruby:jruby`	≥ 9.3.4.0&&< 9.4.12.1	9.4.12.1`org.jruby:jruby:9.4.12.1`
💎RubyGems	`jruby-openssl`	≥ 0.12.1&&< 0.15.4	0.15.4`bundle update jruby-openssl --conservative`

Affected Products

2 products · 3 configurations

Application

jrubyjruby

≥ 9.3.4.0 && < 9.4.12.1

1 version

10.0.0.0

Application

jruby-openssljruby

≥ 0.12.1 && < 0.15.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rubygems:jruby-openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rubygems:jruby-openssl to 0.15.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72qj-48g4-5xgx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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, bot

O3 Security · Impact-Aware SCA

Is GHSA-72qj-48g4-5xgx in your dependencies?

Find it across Maven, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works