CVE-2025-27427: Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission
A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn't have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn't have permission to change the routing-type of the address.
This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0.
Users are recommended to upgrade to version 2.40.0 which fixes the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.apache.activemq:artemis-serverto a version that resolves this vulnerability.Fixed in 2.40.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27427?
CVE-2025-27427 has been classified as a moderate severity vulnerability.
How do I fix CVE-2025-27427?
To remediate CVE-2025-27427, ensure that users do not have the createDurableQueue or createNonDurableQueue permissions without the corresponding createAddress permission.
What software is affected by CVE-2025-27427?
CVE-2025-27427 affects Apache ActiveMQ Artemis versions from 2.0.0 to 2.39.0.
What are the potential impacts of CVE-2025-27427?
Exploit of CVE-2025-27427 can lead to unauthorized changes in routing-type configuration, potentially affecting message delivery.
Who can exploit CVE-2025-27427?
Any user with the createDurableQueue or createNonDurableQueue permission on an address can exploit CVE-2025-27427.