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

Red Hat

Red Hat AMQ Broker 7

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-93562 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93574 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93579 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93573 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93568 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93569 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93567 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93566 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93565 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93564 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93558 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93492 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93491 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93488 18 Sep 2026 See the vendor and CVE records for the affected range. No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-93575 18 Sep 2026 See the vendor and CVE records for the affected range. To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Update reference ↗
CVE-2026-84218 1 Sep 2026 See the vendor and CVE records for the affected range. 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.