https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 13:54:24 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-322949 EUVD-2026-322949 https://cve.radiocsirt.org/vuln/euvd-2026-322949 https://cve.radiocsirt.org/vuln/fkie_cve-2026-40914 <p>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&#39;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&#39;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.</p> <p>This issue affects Apache Artemis: from 2.50.0 through 2.53.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0.</p> <p>Users are recommended to upgrade to version 2.54.0, which fixes the issue.</p> <p>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&#39;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&#39;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.</p> <p>This issue affects Apache Artemis: from 2.50.0 through 2.53.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0.</p> <p>Users are recommended to upgrade to version 2.54.0, which fixes the issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-40914 https://cve.radiocsirt.org/vuln/ghsa-rf99-f9j2-gv3f <p><strong>Affected:</strong> Maven: org.apache.artemis:artemis-stomp-protocol</p> <p>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&#39;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&#39;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.</p> <p>This issue affects Apache Artemis: from 2.50.0 through 2.53.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0.</p> <p>Users are recommended to upgrade to version 2.54.0, which fixes the issue.</p> <p><strong>Affected:</strong> Maven: org.apache.artemis:artemis-stomp-protocol</p> <p>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&#39;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&#39;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.</p> <p>This issue affects Apache Artemis: from 2.50.0 through 2.53.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0.</p> <p>Users are recommended to upgrade to version 2.54.0, which fixes the issue.</p> https://cve.radiocsirt.org/vuln/ghsa-rf99-f9j2-gv3f