CVE-2026-40914: Apache Artemis Stomp Protocol, Apache ActiveMQ Artemis Stomp Protocol: Address routing-type can be updated by STOMP protocol user without the createAddress permission
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Artemisto a version that resolves this vulnerability.Fixed in 2.54.0 - Upgrade
Upgrade
Apache ActiveMQ Artemisto a version that resolves this vulnerability.Fixed in 2.54.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40914?
The severity of CVE-2026-40914 is rated as medium with a CVSS score of 4.3.
How does CVE-2026-40914 affect Apache Artemis?
CVE-2026-40914 allows STOMP protocol users to update the routing-type of an address without having the createAddress permission.
Who is affected by CVE-2026-40914?
Applications using the STOMP protocol in Apache Artemis or Apache ActiveMQ Artemis that grant consume or send permissions are affected by CVE-2026-40914.
How do I mitigate the risk of CVE-2026-40914?
To mitigate the risk of CVE-2026-40914, ensure users with consume or send permissions do not have the ability to augment routing types unless they possess the createAddress permission.
What kind of security implications does CVE-2026-40914 have?
CVE-2026-40914 can lead to unauthorized modifications of address routing, potentially affecting message delivery and system integrity.