CVE-2026-40914
mediumPriorität · verfolgen · 17OT-Risiko · erhöhtEPSS 0.004 · 31. PerzentilEUUSEPSS · bewertet 2026-10-27
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (6)
Betroffene Produkte und Versionsbereiche.
- Maven org.apache.artemis:artemis-stomp-protocol2.0.0 → 2.44.0osvUSpkg:maven/org.apache.artemis/artemis-stomp-protocol
- Maven org.apache.artemis:artemis-stomp-protocol2.50.0 → 2.54.0osvUSpkg:maven/org.apache.artemis/artemis-stomp-protocol
Advisories (1)
Hersteller- und Ökosystem-Meldungen dazu.
- GHSA-rf99-f9j2-gv3fApache Artemis has an Incorrect Authorization issue2026-05-28ghsa · osvUS
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.
auch bekannt als (3)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (5)
Externe Belege — Patches, Meldungen, Analysen.
- http://www.openwall.com/lists/oss-security/2026/05/27/8cnnvd
- https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4ccnnvd
- https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4cenisa_euvd
- http://www.openwall.com/lists/oss-security/2026/05/27/8Mailing ListThird Party Advisorynvd
- https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4cMailing ListVendor Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan