Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
CRITICAL severity

GHSA-rc7h-x6cq-988q jgroups

CRITICALFix: belaban/JGroups@eeaf524

GHSA-rc7h-x6cq-988q is a critical-severity (CVSS 9.8) vulnerability in org.jgroups:jgroups. A fix is available for org.jgroups:jgroups — see the affected versions and patch details below.

Improper Input Validation in JGroups

Also known asCVE-2016-2141
Published
May 13, 2022
Updated
Mar 9, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-rc7h-x6cq-988q plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
org.jgroups:jgroupsorg.jgroups:jgroups

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

JGroups before 4.0 does not require the proper headers for the ENCRYPT and AUTH protocols from nodes joining the cluster, which allows remote attackers to bypass security restrictions and send and receive messages within the cluster via unspecified vectors. Fixes for this issue have been backported to versions 3.6.10.Final and 3.2.16.Final.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.jgroups:jgroups3.3.0.Alpha1&&< 3.6.10.Final3.6.10.Finalorg.jgroups:jgroups:3.6.10.Final
Mavenorg.jgroups:jgroupsall versions3.2.16.Finalorg.jgroups:jgroups:3.2.16.Final

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update org.jgroups:jgroups to 3.6.10.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc7h-x6cq-988q is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rc7h-x6cq-988q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rc7h-x6cq-988q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical
ProductFixed inAdvisory
JBoss Enterprise BRMS Platform 5.3ClusteringRHSA-2016:1345
Red Hat JBoss BRMS 6.3ClusteringRHSA-2016:1347
Red Hat JBoss Data Grid 6.6jgroupsRHSA-2016:1334
Red Hat JBoss Data Virtualization 6.2ClusteringRHSA-2016:1346
Red Hat JBoss EAP 7.0see advisoryRHSA-2016:1333
Red Hat JBoss Enterprise Application Platform 5.2see advisoryRHSA-2016:1329
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5jgroups-1:2.6.22-2.ep5.el5RHSA-2016:1328
Red Hat JBoss Enterprise Application Platform 6.4see advisoryRHSA-2016:1331

Frequently Asked Questions

JGroups before 4.0 does not require the proper headers for the ENCRYPT and AUTH protocols from nodes joining the cluster, which allows remote attackers to bypass security restrictions and send and receive messages within the cluster via unspecified vectors. Fixes for this issue have been backported to versions 3.6.10.Final and 3.2.16.Final.
O3 Security · Impact-Aware SCA

Is GHSA-rc7h-x6cq-988q in your dependencies?

O3 Security finds GHSA-rc7h-x6cq-988q across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rc7h-x6cq-988q: jgroups (Critical 9.8) | O3 Security