JBoss ↗
Auto-added after CISA flagged JBoss as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for JBoss, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
JBoss currently scores 97/100 — healthy. 6 actively-exploited vulnerabilities (CISA KEV) affect older releases (e.g. CVE-2023-44487) — staying on the latest supported version keeps you clear of them. The latest supported release is 8.1.9. It's on the latest patch with no significant known issues — keep it current.
Disclosure trend iNew CVEs published for JBoss each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
3 of its known vulnerabilities are linked to ransomware campaigns (CISA KEV).
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2023-44487 HIGH exploited Uncontrolled resource consumption EPSS 100% → see advisory CVE-2017-12617 HIGH exploited Unrestricted file upload EPSS 100% → see advisory CVE-2017-12149 CRITICAL exploited ransomware Insecure deserialization EPSS 91% → see advisory CVE-2010-1871 HIGH exploited CWE-917 EPSS 83% → see advisory CVE-2010-0738 MEDIUM exploited ransomware CWE-749 EPSS 74% → see advisory CVE-2010-1428 HIGH exploited ransomware CWE-749 EPSS 53% → see advisory CVE-2014-0224 HIGH CWE-326 EPSS 95% → see advisory CVE-2016-2183 HIGH Information disclosure EPSS 95% → see advisory CVE-2023-48795 MEDIUM CWE-354 EPSS 94% → see advisory CVE-2017-12629 CRITICAL XML external entity (XXE) EPSS 92% → see advisory CVE-2019-9515 HIGH Uncontrolled resource consumption EPSS 87% → see advisory CVE-2014-0226 MEDIUM CWE-362 EPSS 86% → see advisoryGet alerted about JBoss
Be emailed the moment JBoss gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for JBoss — no marketing, no sharing, and we never know what you run. Track your whole stack →
Versions & lifecycle iWhen each release line stops receiving security patches (end-of-life). After EOL there are no more fixes — plan upgrades before these dates.
How long each JBoss release line is supported — and when it sunsets. Select a line for its full report.
Full JBoss end-of-life dates & support timeline →
8 latest 8.1.9 Supported until 2031-02-058.1.9 → 7 latest 7.4.25 End of life ended 2025-06-307.4.25 → 6 latest 6.4.24 End of life ended 2019-06-306.4.24 → 5 latest 5.2.0 End of life ended 2016-11-305.2.0 → 4.3 latest 4.3.0 CP10 End of life ended 2013-01-314.3.0 CP10 → 4.2 latest 4.2.0.CP09 End of life ended 2012-06-304.2.0.CP09 → See all upcoming end-of-life dates →Frequently asked
Is JBoss safe and patched?
JBoss currently scores 97/100 — healthy. 6 actively-exploited vulnerabilities (CISA KEV) affect older releases (e.g. CVE-2023-44487) — staying on the latest supported version keeps you clear of them. The latest supported release is 8.1.9. It's on the latest patch with no significant known issues — keep it current.
What should I do about JBoss now?
Upgrade JBoss to the latest supported release (8.1.9) or later, which clears the actively-exploited issues affecting older versions, then confirm against Red Hat's official advisory.
Why is JBoss listed on IsItPatched?
JBoss was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has JBoss been actively exploited?
Yes. CISA added JBoss to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2010-1428. Make sure you are running a patched, supported version of JBoss and confirm it against Red Hat's security advisory.
When does JBoss reach end-of-life?
The latest supported JBoss release is 8.1.9. After end-of-life a release no longer receives security patches.
Which versions of JBoss are still receiving security updates?
Supported JBoss release lines (latest 8.1.9): 8. End-of-life releases no longer receive security patches.
Similar software we track
More from Red Hat tracked on IsItPatched.
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 — JBoss official site ↗