A vulnerability exists in Apache Artemis whereby an application using the STOMP protocol with security credentials that grant either the consume or send 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. A user could successfully send a message to an address or consume a message from a queue with a routing-type not supported by the corresponding address when that operation should actually be rejected on the basis that the user doesn't have permission to change the routing-type of the address. Even though the user was already granted permission to send and/or consume messages, they should not be able to augment the routing-type of the address without the createAddress permission. This issue affects Apache Artemis: from 2.50.0 through 2.53.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0. Users are recommended to upgrade to version 2.54.0, which fixes the issue.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4c Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 4.3 · apacheNVD modified 2026-10-14 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:artemis:*:*:*:*:*:*:*:*
References 2
- https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4c Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/05/27/8 Mailing List, Third Party Advisory