How severe is CVE-2025-46551?

CVE-2025-46551 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2025-46551 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-46551?

CVE-2025-46551 primarily affects Jruby. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-46551?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-46551 have an EU (EUVD) identifier?

Yes. CVE-2025-46551 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-13880.

When was CVE-2025-46551 published?

CVE-2025-46551 was published on 2025-05-07 and last updated on 2026-06-17.

CVE-2025-46551

CVE-2025-46551 is a low-severity vulnerability in Jruby with a CVSS 3.x base score of 3.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
CVSS v4: 5.7
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-13880
Weakness: CWE-295
Affected product: Jruby
Published: 2025-05-07
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-46551?: 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.
How severe is CVE-2025-46551?: CVE-2025-46551 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2025-46551 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-46551?: CVE-2025-46551 primarily affects Jruby. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-46551?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-46551 have an EU (EUVD) identifier?: Yes. CVE-2025-46551 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-13880.
When was CVE-2025-46551 published?: CVE-2025-46551 was published on 2025-05-07 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:jruby:jruby:*:*:*:*:*:*:*:*
cpe:2.3:a:jruby:jruby:10.0.0.0:*:*:*:*:*:*:*
cpe:2.3:a:jruby:jruby-openssl:*:*:*:*:*:*:*:*

More vulnerabilities in Jruby

CVE-2012-5370 — Medium (CVSS 5.0): JRuby computes hash values without properly restricting the ability to trigger hash collisions predictably, which…
CVE-2011-4838 — Medium (CVSS 5.0): JRuby before 1.6.5.1 computes hash values without restricting the ability to trigger hash collisions predictably, which…
CVE-2010-1330 — Medium (CVSS 4.3): The regular expression engine in JRuby before 1.4.1, when $KCODE is set to 'u', does not properly handle characters…

All CVEs affecting Jruby →

Other CWE-295 (Improper Certificate Validation) vulnerabilities

CVE-2026-4370 — Critical (CVSS 10.0): A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the…
CVE-2026-30836 — Critical (CVSS 10.0): Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6…
CVE-2025-68121 — Critical (CVSS 10.0): During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…
CVE-2022-20703 — Critical (CVSS 10.0): Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker…
CVE-2021-1471 — Critical (CVSS 9.9): Multiple vulnerabilities in Cisco Jabber for Windows, Cisco Jabber for MacOS, and Cisco Jabber for mobile platforms…
CVE-2026-20184 — Critical (CVSS 9.8): A vulnerability in the integration of single sign-on (SSO) with Control Hub in Cisco Webex Services could have allowed…

Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →