Skip to main content
← All vulnerabilities
CVE-2026-40914GHSA-RF99-F9J2-GV3F

Apache Artemis Stomp Protocol, Apache ActiveMQ Artemis Stomp Protocol: Address routing-type can be updated by STOMP protocol user without the createAddress permission

Published
Last modified
published
Not listed in CISA KEV
Low (apache)
Fix
Fixed in 2.54.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • org.apache.artemis:artemis-stomp-protocol

    From 2.50.0 · through 2.53.0

  • org.apache.artemis:artemis-stomp-protocol

    From 2.0.0 · through 2.44.0

  • org.apache.artemis:artemis-stomp-protocolMaven

    From 2.50.0 · fixed in 2.54.0

  • org.apache.artemis:artemis-stomp-protocolMaven

    From 2.0.0 · through 2.44.0

References 1

lists.apache.org