Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY9 SECURITY RECORDS

Apache Software Foundation

Apache Artemis

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-49362 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-49363 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-49364 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-57822 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.3.0 ≤ 2.44.0 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-2026-57967 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-67593 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0, 2.32.0 ≤ 2.44.0 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-2026-75880 10 Sep 2026 Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-32642 24 Mar 2026 2.50.0 ≤ 2.52.0; 2.0.0 ≤ 2.44.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-27446 4 Mar 2026 Apache Artemis: 2.50.0 ≤ 2.51.0; Apache ActiveMQ Artemis: 2.11.0 ≤ 2.44.0 RHSA-2026:53644: Red Hat JBoss EAP 7.4 ELS for RHEL 7 Server Update reference ↗

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.