Is JBoss 6.4.24 patched?
Current stable (8.1.9): 97/100
6.4.24 has 3 open critical-or-high vulnerabilities. Run 7.2.4 or later to clear them. See what 7.2.4 fixes →
Upgrade impact: Major upgrade. Crossing a major version usually means breaking changes. Review the vendor’s upgrade / migration guide and test before you roll it out.
Summary iPlain-English security status for JBoss 6.4.24, built from its CVEs, active-exploitation data, end-of-life date and latest release.
JBoss 6.4.24 is part of the 6.4 release line. 7 known vulnerabilities affect it. The minimum safe version is 7.2.4 — upgrade to it or later to clear the open critical/high issues. The latest supported JBoss release is 8.1.9.
Known issues affecting 6.4.24
Exploited first, then by exploitation probability.
CVE-2016-5406 HIGH EPSS 3% → see advisory CVE-2016-4993 MEDIUM EPSS 3% → see advisory CVE-2016-7061 LOW EPSS 2% → fixed in 7.0.4 CVE-2019-19343 HIGH EPSS 2% → fixed in 7.2.4 CVE-2019-14885 MEDIUM EPSS 1% → fixed in 7.2.6 CVE-2017-12167 MEDIUM EPSS 0% → fixed in 7.0.9 CVE-2016-7066 HIGH EPSS 0% → fixed in 7.1.0Other JBoss versions
Check another release line of JBoss.
Frequently asked
Is JBoss 6.4.24 patched?
JBoss 6.4.24 has 3 open critical-or-high vulnerabilities. The minimum safe version is 7.2.4 — upgrade to 7.2.4 or later to clear them.
What version should I upgrade JBoss 6.4.24 to?
Upgrade JBoss 6.4.24 to at least 7.2.4 to clear its 3 open critical-or-high vulnerabilities.
What is the latest version of JBoss?
The latest supported JBoss release is 8.1.9.
Is JBoss 6.4.24 still receiving security updates?
Yes — the 6.4 line is still supported and receiving security updates. The latest release is 8.1.9.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Red Hat's official advisory before you patch or upgrade.