How severe is CVE-2016-2141?

CVE-2016-2141 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-2141?

CVE-2016-2141 affects the following packages: org.jgroups:jgroups (Maven), org.jgroups:jgroups (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-2141?

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 CVE-2016-2141 is resolved across your whole dependency graph.

How do I detect CVE-2016-2141 in my Maven dependencies?

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.

How do I mitigate CVE-2016-2141 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2016-2141 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-2141 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 CVE-2016-2141?

CVE-2016-2141 has an EPSS (Exploit Prediction Scoring System) score of 4.7%, placing it in the 92th 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.

When was CVE-2016-2141 published, and has it been updated?

CVE-2016-2141 was published on June 30, 2016 and was last updated on March 15, 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

Not in CISA KEV

CRITICAL severity

CVE-2016-2141 — jgroups

CRITICALFix: belaban/JGroups@eeaf524

CVE-2016-2141 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 asGHSA-rc7h-x6cq-988q

Published

Jun 30, 2016

Updated

Mar 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 3, 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 CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.jgroups:jgroups☕org.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

It was found that JGroups did not require necessary headers for encrypt and auth protocols from new nodes joining the cluster. An attacker could use this flaw to bypass security restrictions, and use this vulnerability to send and receive messages within the cluster, leading to information disclosure, message spoofing, or further possible attacks.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jgroups:jgroups`	≥ 3.3.0.Alpha1&&< 3.6.10.Final	3.6.10.Final`org.jgroups:jgroups:3.6.10.Final`
☕Maven	`org.jgroups:jgroups`	all versions	3.2.16.Final`org.jgroups:jgroups:3.2.16.Final`

Affected Products

2 products · 4 configurations

Application

jboss enterprise application platformredhat

3 versions

5.26.47.0

Application

jgroupsredhat

< 4.0

range

Detection & mitigation playbook

Open-source dependency

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.
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 CVE-2016-2141 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Workaround published by Red Hat

Please refer to https://access.redhat.com/articles/2360521 for more information.

Source: Red Hat security advisory for CVE-2016-2141 (CC BY 4.0)

Product	Fixed in	Advisory
JBoss Enterprise BRMS Platform 5.3	`Clustering`	RHSA-2016:1345
Red Hat JBoss BRMS 6.3	`Clustering`	RHSA-2016:1347
Red Hat JBoss Data Grid 6.6	`jgroups`	RHSA-2016:1334
Red Hat JBoss Data Virtualization 6.2	`Clustering`	RHSA-2016:1346
Red Hat JBoss EAP 7.0	see advisory	RHSA-2016:1333
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2016:1329
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`jgroups-1:2.6.22-2.ep5.el5`	RHSA-2016:1328
Red Hat JBoss Enterprise Application Platform 6.4	see advisory	RHSA-2016:1331

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-2141 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works