CVE-2025-27427
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk39th percentile - higher than 39% of all known CVEs
Summary
A vulnerability exists in Apache ActiveMQ Artemis that allows a user with permissions to create queues to modify the routing type of an address, even if they do not have permission to create that address. This could lead to sending messages with a routing type not supported by the address.
Risk Assessment
The organization may be exposed to unauthorized changes in message routing, potentially leading to unexpected system behavior and security breaches.
Recommendation
It is recommended to upgrade to version 2.40.0, which fixes the issue.
Other vulnerabilities in Apache ActiveMQ Artemis
See all- CVE-2023-50780High
Apache ActiveMQ Artemis before version 2.29.0 allows access to diagnostic information and controls through MBeans, including the Log4J2 MBean, which is not meant for exposure to non-administrative users. This could allow an authenticated attacker to write arbitrary files to the filesystem and indirectly achieve RCE.
- CVE-2016-4978High
The getObject method of the javax.jms.ObjectMessage class in Apache ActiveMQ Artemis before version 1.4.0 may allow remote authenticated users with permission to send messages to the Artemis broker to deserialize arbitrary objects and execute arbitrary code.
- CVE-2025-27391Medium
The vulnerability in Apache ActiveMQ Artemis involves the insertion of sensitive information into the log file. All broker property values are logged when the org.apache.activemq.artemis.core.config.impl.ConfigurationImpl logger has debug level enabled.
- CVE-2022-35278Medium
In Apache ActiveMQ Artemis prior to version 2.24.0, an attacker could show malicious content and/or redirect users to a malicious URL in the web console by using HTML in the name of an address or queue.
- CVE-2022-23913High
In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory.
- CVE-2021-26118High
In the OpenWire protocol of Apache ActiveMQ Artemis 2.15.0, a vulnerability was found that allowed bypassing policy-based access control when creating advisory messages for the entire session. The production of these messages was not subject to access control in error.
- CVE-2020-13932Medium
In Apache ActiveMQ Artemis versions 2.5.0 to 2.13.0, there is an XSS vulnerability that can be exploited through a specially crafted MQTT packet containing an XSS payload in the client-id or topic name. The XSS payload is injected into the admin console's browser.
Original NVD description (English source)
A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue 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. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn't have permission to change the routing-type of the address. This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0. Users are recommended to upgrade to version 2.40.0 which fixes the issue.