Apache
ActiveMQ
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Apache ActiveMQ Classic. Use that record for publisher support phases and retirement dates.
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-2026-34197 | 7 Apr 2026 | Apache ActiveMQ Broker: < 5.19.4, 6.0.0 < 6.2.3; Apache ActiveMQ All: < 5.19.4, 6.0.0 < 6.2.3; Apache ActiveMQ: < 5.19.4, 6.0.0 < 6.2.3 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-46604 | 27 Oct 2023 | Apache ActiveMQ: 5.18.0 < 5.18.3, 5.17.0 < 5.17.6, 5.16.0 < 5.16.7, < 5.15.16; Apache ActiveMQ Legacy OpenWire Module: 5.18.0 < 5.18.3, 5.17.0 < 5.17.6, 5.16.0 < 5.16.7, 5.8.0 < 5.15.16 | The RHEL-7 based Middleware Containers container image provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog (see References). Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally. | Update reference ↗ |
| CVE-2015-7559 | 1 Aug 2019 | 5.15.5 | 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-2016-3088 | 1 Jun 2016 | n/a | 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 ↗ |
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.