JBoss vulnerabilities: known CVEs & security history
Red Hat · Actively exploited · 243 tracked CVEs · 6 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all JBoss release lines — 243 in total, with 6 actively exploited in the wild. A CVE here doesn't mean your version is affected — check JBoss's current status and the safe version to run.
Known JBoss CVEs
Actively-exploited and most-severe first. Showing the top 80 of 243. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2017-12149⚡ exploited | critical | 9.8 | 91% | 2017 |
| CVE-2010-1871⚡ exploited | high | 8.8 | 83% | 2010 |
| CVE-2017-12617⚡ exploited | high | 8.1 | 100% | 2017 |
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2010-1428⚡ exploited | high | 7.5 | 62% | 2010 |
| CVE-2010-0738⚡ exploited | medium | 5.3 | 79% | 2010 |
| CVE-2018-14721 | critical | 10 | 10% | 2019 |
| CVE-2019-14892 | critical | 9.8 | 5% | 2020 |
| CVE-2019-17531 | critical | 9.8 | 5% | 2019 |
| CVE-2019-17267 | critical | 9.8 | 5% | 2019 |
| CVE-2019-10212 | critical | 9.8 | 2% | 2019 |
| CVE-2019-16943 | critical | 9.8 | 5% | 2019 |
| CVE-2019-16942 | critical | 9.8 | 6% | 2019 |
| CVE-2019-10202 | critical | 9.8 | 5% | 2019 |
| CVE-2019-16335 | critical | 9.8 | 5% | 2019 |
| CVE-2019-14540 | critical | 9.8 | 11% | 2019 |
| CVE-2019-14379 | critical | 9.8 | 8% | 2019 |
| CVE-2018-14720 | critical | 9.8 | 8% | 2019 |
| CVE-2018-8088 | critical | 9.8 | 15% | 2018 |
| CVE-2018-7489 | critical | 9.8 | 21% | 2018 |
| CVE-2017-7525 | critical | 9.8 | 38% | 2018 |
| CVE-2017-15095 | critical | 9.8 | 8% | 2018 |
| CVE-2017-17485 | critical | 9.8 | 50% | 2018 |
| CVE-2015-7501 | critical | 9.8 | 83% | 2017 |
| CVE-2017-12629 | critical | 9.8 | 92% | 2017 |
| CVE-2016-3690 | critical | 9.8 | 5% | 2017 |
| CVE-2017-7504 | critical | 9.8 | 29% | 2017 |
| CVE-2017-7503 | critical | 9.8 | 2% | 2017 |
| CVE-2016-2141 | critical | 9.8 | 5% | 2016 |
| CVE-2025-12543 | critical | 9.6 | 1% | 2026 |
| CVE-2019-14887 | critical | 9.1 | 1% | 2020 |
| CVE-2019-20445 | critical | 9.1 | 13% | 2020 |
| CVE-2019-20444 | critical | 9.1 | 9% | 2020 |
| CVE-2016-5018 | critical | 9.1 | 10% | 2017 |
| CVE-2017-9788 | critical | 9.1 | 57% | 2017 |
| CVE-2017-7465 | critical | 9 | 3% | 2018 |
| CVE-2021-32027 | high | 8.8 | 2% | 2021 |
| CVE-2019-14843 | high | 8.8 | 1% | 2020 |
| CVE-2019-10174 | high | 8.8 | 3% | 2019 |
| CVE-2019-3894 | high | 8.8 | 2% | 2019 |
| CVE-2016-7065 | high | 8.8 | 12% | 2016 |
| CVE-2016-5406 | high | 8.8 | 3% | 2016 |
| CVE-2026-28369 | high | 8.7 | 1% | 2026 |
| CVE-2026-28368 | high | 8.7 | 1% | 2026 |
| CVE-2026-28367 | high | 8.7 | 1% | 2026 |
| CVE-2017-7464 | high | 8.7 | 2% | 2018 |
| CVE-2026-3009 | high | 8.1 | 0% | 2026 |
| CVE-2025-23368 | high | 8.1 | 1% | 2025 |
| CVE-2020-1757 | high | 8.1 | 2% | 2020 |
| CVE-2018-8039 | high | 8.1 | 10% | 2018 |
| CVE-2018-5968 | high | 8.1 | 7% | 2018 |
| CVE-2021-3717 | high | 7.8 | 0% | 2022 |
| CVE-2012-2312 | high | 7.8 | 0% | 2019 |
| CVE-2016-7066 | high | 7.8 | 0% | 2018 |
| CVE-2016-8657 | high | 7.8 | 0% | 2018 |
| CVE-2017-12189 | high | 7.8 | 0% | 2018 |
| CVE-2017-2595 | high | 7.7 | 3% | 2018 |
| CVE-2025-9784 | high | 7.5 | 2% | 2025 |
| CVE-2024-7885 | high | 7.5 | 3% | 2024 |
| CVE-2024-1635 | high | 7.5 | 5% | 2024 |
| CVE-2023-3171 | high | 7.5 | 1% | 2023 |
| CVE-2023-5379 | high | 7.5 | 1% | 2023 |
| CVE-2023-3223 | high | 7.5 | 2% | 2023 |
| CVE-2023-1108 | high | 7.5 | 2% | 2023 |
| CVE-2022-4492 | high | 7.5 | 1% | 2023 |
| CVE-2022-1259 | high | 7.5 | 1% | 2022 |
| CVE-2021-3859 | high | 7.5 | 1% | 2022 |
| CVE-2021-3690 | high | 7.5 | 1% | 2022 |
| CVE-2022-0853 | high | 7.5 | 1% | 2022 |
| CVE-2021-4104 | high | 7.5 | 81% | 2021 |
| CVE-2020-25710 | high | 7.5 | 3% | 2021 |
| CVE-2019-19343 | high | 7.5 | 2% | 2021 |
| CVE-2020-25644 | high | 7.5 | 2% | 2020 |
| CVE-2020-14384 | high | 7.5 | 1% | 2020 |
| CVE-2020-10705 | high | 7.5 | 1% | 2020 |
| CVE-2020-7238 | high | 7.5 | 4% | 2020 |
| CVE-2012-5626 | high | 7.5 | 1% | 2020 |
| CVE-2019-14888 | high | 7.5 | 2% | 2020 |
| CVE-2019-10172 | high | 7.5 | 17% | 2019 |
| CVE-2019-0210 | high | 7.5 | 7% | 2019 |
163 older / lower-severity CVEs not shown — see JBoss's full record.
Is my JBoss version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your JBoss version → · Monitor JBoss for new CVEs →
JBoss vulnerabilities — frequently asked
How many known vulnerabilities does JBoss have?
IsItPatched tracks 243 CVEs for JBoss, 6 of which are actively exploited (CISA KEV). 31 are critical-severity and 86 high-severity. These span every release line — what matters is whether the version you run is affected.
Does JBoss have any actively-exploited vulnerabilities?
Yes — 6 JBoss CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (3 linked to ransomware). Patch these as a priority.
What is the most severe JBoss vulnerability?
Among tracked issues, CVE-2017-12149 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Insecure deserialization weakness.
Is JBoss safe to use?
It depends on the version. The latest supported JBoss release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: JBoss security status · JBoss end-of-life · actively-exploited CVEs. Always verify against Red Hat's advisories — see our disclaimer.