High [CVE-2026-54475] Information disclosure due to broken temporary destination isolation
This high-severity Red Hat Linux advisory covers CVE-2026-54475 affecting Red Hat Fuse 7.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Missing Authorization vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Apache ActiveMQ Classic temporary destinations are expected to be isolated to the connection that created them.
The isolation can be broken as this is only checked in the client, allowing a different connection to consume from another connection's temporary destination. Users are recommended to upgrade to version 6.2.7, which fixes the issue.
Temporary destinations, which are designed to be private to a specific connection, can be accessed by other connections due to a missing authorization check. This allows an unauthorized connection to consume messages from another connection's temporary destination, leading to information disclosure.
Red Hat products ship Apache ActiveMQ Classic components as transitive dependencies. Red Hat AMQ Broker is based on Apache ActiveMQ Artemis, which has its own temporary destination implementation.
The Classic broker's temporary destination logic is not exercised at runtime in Red Hat product deployments. Red Hat severity: Important — CVSS 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L).
Weakness: CWE-1220. Affected Red Hat products: Red Hat Fuse 7.
Red Hat lists Red Hat AMQ Broker 7; Red Hat Data Grid 8; Red Hat Enterprise Linux 8; Red Hat JBoss Enterprise Application Platform Expansion Pack as not affected.
- < 5.19.8
- < 6.0.0
- < 6.2.7
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.