Is CVE-2026-40914 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40914 being exploited in the wild.

How severe is CVE-2026-40914?

Medium severity, with a CVSS score of 4.3, published 28 May 2026.

Which products and versions are affected?

Apache Activemq Artemis 2.0.0 through 2.44.0, 2.50.0 through 2.53.0; org.apache.artemis:artemis-stomp-protocol (Maven) ECOSYSTEM:introduced=2.50.0,fixed=2.54.0.

Is there a fix for CVE-2026-40914?

Yes. org.apache.artemis:artemis-stomp-protocol (Maven): upgrade to 2.54.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-40914 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-40914?

Check whether you run Apache Activemq Artemis or org.apache.artemis:artemis-stomp-protocol (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40914: Apache Artemis authorization bypass in STOMP protocol

CVE-2026-40914 · Severity: medium · CVSS 4.3 · Published 2026-05-28

Apache Artemis, a high-performance message broker used for enterprise messaging, contains a security flaw in its handling of the STOMP protocol. Users with basic permissions to send or receive messages can bypass restrictions to modify how message addresses are routed, even if they lack the specific authority to create or manage those addresses. This could allow unauthorized users to alter message delivery behavior, potentially disrupting standard operations or bypassing intended architectural constraints.

Technologies: Apache Activemq Artemis. Vendors: Apache, Maven.

Quick answers

Is CVE-2026-40914 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40914 being exploited in the wild.
How severe is CVE-2026-40914?: Medium severity, with a CVSS score of 4.3, published 28 May 2026.
Which products and versions are affected?: Apache Activemq Artemis 2.0.0 through 2.44.0, 2.50.0 through 2.53.0; org.apache.artemis:artemis-stomp-protocol (Maven) ECOSYSTEM:introduced=2.50.0,fixed=2.54.0.
Is there a fix for CVE-2026-40914?: Yes. org.apache.artemis:artemis-stomp-protocol (Maven): upgrade to 2.54.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40914 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-40914?: Check whether you run Apache Activemq Artemis or org.apache.artemis:artemis-stomp-protocol (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.artemis:artemis-stomp-protocol (Maven): upgrade to 2.54.0 or later

# set org.apache.artemis:artemis-stomp-protocol to 2.54.0 in your pom.xml or build.gradle

Technical details

An incorrect authorization vulnerability (CWE-863) exists in the STOMP protocol implementation of Apache Artemis. The flaw stems from the STOMP component duplicating auto-creation logic instead of using the centralized ServerSession checkAutoCreate method. An authenticated attacker with 'send' or 'consume' permissions can provide a routing-type not supported by a specific address, effectively augmenting the address configuration without possessing the 'createAddress' permission. This allows for unauthorized modification of address metadata and routing behavior. The issue is resolved in version 2.54.0 by refactoring the STOMP implementation to utilize standard session authorization checks.

Affected products

Apache Artemis 2.50.0 - 2.53.0
Apache ActiveMQ Artemis 2.0.0 - 2.44.0

Identifiers

CVE-2026-40914
GHSA-rf99-f9j2-gv3f

Timeline

2026-04-29: patched: Fix merged into main branch
2026-05-27: disclosed: Public disclosure on oss-security mailing list
2026-05-28: advisory: GitHub Advisory and NVD entry published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.