Answer in brief
CVE-2026-40914 records a Medium severity (CVSS 4.3) vulnerability in Apache Artemis has an Incorrect Authorization issue. The current sources do not mark it as known exploited. The current feed maps org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven), org.apache.artemis:artemis-stomp-protocol (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.artemis:artemis-stomp-protocolmaven | >=2.50.0,<=2.53.0 | 2.54.0 |
| org.apache.artemis:artemis-stomp-protocolmaven | >=2.0.0,<=2.44.0 | Not reported |
| org.apache.artemis:artemis-stomp-protocolmaven | >=2.50.0 <2.54.0 | 2.54.0 |
| org.apache.artemis:artemis-stomp-protocolmaven | >=2.0.0 | Not reported |
Published upstream
May 28, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.