Apache ActiveMQ Broker: Missing Authorization
CVE-2026-54475 is a high-severity missing authorization vulnerability in Apache ActiveMQ Broker from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 5.19.8, 6.2.7 as the first without the flaw, so updating Apache ActiveMQ Broker to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache ActiveMQ Broker to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Update Apache ActiveMQ All to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Update Apache ActiveMQ to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache ActiveMQ Broker | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Apache ActiveMQ All | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Apache ActiveMQ | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Activemq | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Activemq Broker | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CISA (ADP).
Official description
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. This issue affects Apache ActiveMQ Broker: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7. Users are recommended to upgrade to version 6.2.7, which fixes the issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- openwall.com/lists/oss-security/2026/06/29/15Third Party Advisory
Other vulnerabilities in Apache ActiveMQ Broker
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 8.1 High severity
Recent Missing Authorization vulnerabilities
- 8.1 High severity
- 8.8 High severity
- 8.8 High severity
- 8.3 High severity
- 8.8 High severity
- 9.4 Critical severity
Spotted an error? Tell us.