Threat Intelligence Database

Apache ActiveMQ contains a cross-site scripting (XSS) vulnerability in its web console API's MessageServlet. The servlet copies JMS message properties into HTTP response headers without validation, allowing potential injection or overwriting of security headers. This affects Apache ActiveMQ versions before 5.19.7 and versions from 6.0.0 before 6.2.6. The vulnerability has a medium severity rating with a CVSS score of 6.1. The MessageServlet has been deprecated and disabled by default in fixed versions. Users are advised to upgrade to Apache ActiveMQ 5.19.7 or 6.2.6 or later to remediate this issue.

CVE-2026-41043 is a medium severity cross-site scripting (XSS) vulnerability in Apache ActiveMQ and its web console. An authenticated attacker can inject malicious HTML content by overriding the content type and injecting HTML into a JMS selector field when browsing queues. This vulnerability affects Apache ActiveMQ versions before 5.19.6 and from 6.0.0 before 6.2.5. The issue allows limited impact on confidentiality and integrity but does not affect availability.

Improper validation and restriction of a classpath path name vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ. In two instances (when creating a Stomp consumer and also browsing messages in the Web console) an authenticated user provided "key" value could be constructed to traverse the classpath due to path concatenation. As a result, the application is exposed to a classpath path resource loading vulnerability that could potentially be chained together with another attack to lead to exploit. This issue affects Apache ActiveMQ Client: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Broker: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ All: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Web: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ: before 5.19.3, from 6.0.0 before 6.2.2. Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue. Note: 5.19.3 and 6.2.2 also fix this issue, but that is limited to non-Windows environments due to a path separator resolution bug fixed in 5.19.4 and 6.2.3.