First published: Mon Mar 31 2025(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache ActiveMQ Artemis | >=2.0.0<=2.39.0 | |
maven/org.apache.activemq:artemis-server | >=2.0.0<2.40.0 | 2.40.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-27427 has been classified as a moderate severity vulnerability.
To remediate CVE-2025-27427, ensure that users do not have the createDurableQueue or createNonDurableQueue permissions without the corresponding createAddress permission.
CVE-2025-27427 affects Apache ActiveMQ Artemis versions from 2.0.0 to 2.39.0.
Exploit of CVE-2025-27427 can lead to unauthorized changes in routing-type configuration, potentially affecting message delivery.
Any user with the createDurableQueue or createNonDurableQueue permission on an address can exploit CVE-2025-27427.