← Search results
CVE-LINKED INVENTORY13 SECURITY RECORDS
Publisher not identified
WildFly
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-1278 | 13 Sep 2022 | no fixed versions known | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update). | Update reference ↗ |
| CVE-2021-3717 | 24 May 2022 | wildfly-core 17.0 | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-0866 | 10 May 2022 | JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled. | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3503 | 18 Apr 2022 | Fixed in 23.0.1.Final | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-1719 | 7 Jun 2021 | wildfly 20.0.0.Final | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14317 | 2 Jun 2021 | will not be fixed | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3536 | 20 May 2021 | Wildfly 23.0.2.Final | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-20250 | 13 May 2021 | jboss-ejb-client 4.0.39 | Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2020-27822 | 8 Dec 2020 | 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final | Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2020-25640 | 24 Nov 2020 | Wildfly 21.0.0.Final | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14338 | 17 Sep 2020 | All xerces jboss versions before 2.12.0.SP3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10718 | 16 Sep 2020 | before wildfly-embedded-13.0.0.Final | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-1748 | 16 Sep 2020 | before wildfly-elytron-1.6.8.Final-redhat-00001 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.