CVE Intelligence
Medium Access control

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

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.

Published May 28, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: apache

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.6% (30-day exploitation probability)+7
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.56%
ahead of 45% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Apache ActiveMQ Artemis Stomp Protocol and 3 more
CVSS base
4.3
Medium · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.apache.artemis:artemis-stomp-protocol: fixed in version 2.54.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Apache ActiveMQ Artemis Stomp Protocol, Apache Software Foundation Apache Artemis Stomp Protocol, Apache Software Foundation Artemis…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Apache ActiveMQ Artemis Stomp Protocol ≥ 2.0.0 and ≤ 2.44.0 Vulnerable CVE Program (cve.org) e CISA ADP
Apache Software Foundation Apache Artemis Stomp Protocol ≥ 2.50.0 and ≤ 2.53.0 Vulnerable CVE Program (cve.org) e CISA ADP
Apache Software Foundation Artemis ≥ 2.0.0 and ≤ 2.44.0≥ 2.50.0 and < 2.54.0 Vulnerable NIST National Vulnerability Database
Maven Org.apache.artemis:artemis-stomp-protocol ≥ 2.50.0 and ≤ 2.53.0≥ 2.0.0 and ≤ 2.44.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.3 CVSS 3.1 Medium 2.8 1.4 nvd@nist.gov via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium 2.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 3.1 Medium — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.56%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.apache.artemis:artemis-stomp-protocol
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · apache software foundation/apache artemis stomp protocol, apache software foundation/apache activemq artemis stomp proto
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 4.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 28, 2026 · apache

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
Access control
same class
CWE-863
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-57967 Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment Sep 10, 2026
  • CVE-2026-32642 Apache Artemis, Apache ActiveMQ Artemis: Temporary address auto-created for OpenWire consumer without createAddress permission Mar 24, 2026
  • CVE-2026-27446 Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation Mar 4, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-40914 is "Apache Artemis Stomp Protocol, Apache ActiveMQ Artemis Stomp Protocol: Address routing-type can be updated by STOMP protocol user without the createAddress permission", rated Medium. It affects Apache ActiveMQ Artemis Stomp Protocol (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.56% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.