CVE-2016-2141

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 15% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
90.7%
KEV
Not listed

Published

June 30, 2016

Last Modified

May 6, 2026

Advisory Details (9)

Auto-updated May 8, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:1376
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:1374
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:1347
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:1346
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:1345
generic
http://www.securityfocus.com/bid/91481
generic
http://rhn.redhat.com/errata/RHSA-2016-2035.html
generic
http://rhn.redhat.com/errata/RHSA-2016-1439.html
generic
http://rhn.redhat.com/errata/RHSA-2016-1435.html

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2016-10-06redhat
redhatpatch2016-07-19redhat
redhatjboss-ec2-eap-0:7.5.9-2.Final_redhat_2.ep6.el62016-07-18redhat
redhatxalan-j2-eap6-0:2.7.1-11.redhat_11.1.ep6.el62016-07-18redhat
redhatxalan-j2-eap6-0:2.7.1-11.redhat_11.1.ep6.el72016-07-18redhat
redhatpatch2016-07-18redhat
redhatClustering2016-07-07redhat
redhatjgroups-1:3.2.16-1.Final_redhat_1.1.ep6.el72016-06-23redhat
redhatpatch2016-06-23redhat
redhatJGroups2016-06-23redhat
redhatpatch2016-06-23redhat
redhateap7-jgroups-0:3.6.8-3.Final_redhat_3.1.ep7.el72016-06-23redhat
redhatjgroups-1:2.6.22-2.ep5.el62016-06-23redhat
redhatpatch2016-06-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jgroups:jgroups2.10.0.CR1 ... 3.2.9.Final (78 versions)3.2.16.Final—

All Vendor Advisories

(19)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-12 05:43 UTCEPSS rescore
  3. 2026-07-11 08:23 UTCEPSS rescore
  4. 2026-07-09 19:05 UTCEPSS rescore
  5. 2026-07-08 15:10 UTCEPSS rescore
  6. 2026-07-08 14:45 UTCOSV refresh
  7. 2026-07-07 13:42 UTCEPSS rescore
  8. 2026-07-06 16:24 UTCEPSS rescore
  9. 2026-07-06 16:24 UTCEPSS rescore
  10. 2026-07-06 02:20 UTCEPSS rescore
  11. 2026-07-06 02:20 UTCEPSS rescore
  12. 2026-07-05 02:27 UTCEPSS rescore
  13. 2026-07-04 06:28 UTCEPSS rescore
  14. 2026-07-01 15:02 UTCEPSS rescore
  15. 2026-06-30 23:19 UTCEPSS rescore
  16. 2026-06-29 14:03 UTCEPSS rescore
  17. 2026-06-28 14:04 UTCEPSS rescore
  18. 2026-06-28 04:53 UTCEPSS rescore
  19. 2026-06-27 03:05 UTCEPSS rescore
  20. 2026-06-27 03:05 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-24 14:02 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 14:54 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-20 02:42 UTCOSV refresh
  6. 2026-06-19 19:23 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-17 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:14 UTCEPSS rescore
  15. 2026-06-13 22:57 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-11 13:57 UTCEPSS rescore
  20. 2026-06-10 22:15 UTCEPSS rescore
  21. 2026-06-10 13:18 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-05 22:44 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-04 13:10 UTCEPSS rescore
  31. 2026-06-02 20:10 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-06-01 13:49 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 22:28 UTCEPSS rescore
  36. 2026-05-31 03:55 UTCOSV refresh
  37. 2026-05-31 00:14 UTCEPSS rescore
  38. 2026-05-29 13:41 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-27 13:38 UTCEPSS rescore
  43. 2026-05-26 13:42 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-24 16:43 UTCEPSS rescore
  46. 2026-05-23 00:10 UTCEG score recompute
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-22 21:15 UTCEPSS rescore
  49. 2026-05-21 22:40 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 22:37 UTCEPSS rescore
  53. 2026-05-20 11:21 UTCEPSS rescore
  54. 2026-05-20 11:21 UTCEPSS rescore
  55. 2026-05-20 11:21 UTCEPSS rescore
  56. 2026-05-20 11:03 UTCEG score recompute
  57. 2026-05-20 11:03 UTCVendor advisory
  58. 2026-05-20 07:19 UTCEG score recompute
  59. 2026-05-20 07:19 UTCVendor advisory
  60. 2026-05-20 03:34 UTCEG score recompute
  61. 2026-05-20 03:34 UTCVendor advisory
  62. 2026-05-19 23:50 UTCEG score recompute
  63. 2026-05-19 23:50 UTCVendor advisory
  64. 2026-05-19 20:05 UTCEG score recompute
  65. 2026-05-19 20:05 UTCVendor advisory
  66. 2026-05-19 16:17 UTCEG score recompute
  67. 2026-05-19 16:17 UTCVendor advisory
  68. 2026-05-19 12:29 UTCEG score recompute
  69. 2026-05-19 12:29 UTCVendor advisory
  70. 2026-05-19 08:33 UTCEG score recompute
  71. 2026-05-19 08:33 UTCVendor advisory
  72. 2026-05-19 04:43 UTCEG score recompute
  73. 2026-05-19 04:43 UTCVendor advisory
  74. 2026-05-19 00:54 UTCEG score recompute
  75. 2026-05-19 00:54 UTCVendor advisory

Frequently asked(5)

What is CVE-2016-2141?
CVE-2016-2141 is a critical vulnerability published on June 30, 2016. 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…
When was CVE-2016-2141 disclosed?
CVE-2016-2141 was first published in the National Vulnerability Database on June 30, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-2141 actively exploited?
CVE-2016-2141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-2141?
CVE-2016-2141 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-2141?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2141, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-2141

Explore →

Is Your Infrastructure Affected by CVE-2016-2141?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs