CVE-2026-33227: Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ: Improper Limitation of a Pathname to a Restricted Classpath Directory

Published Apr 6, 2026
·
Updated

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.

Other sources

Improper validation and restriction of a classpath path name vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All.

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.

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.

— GitHub

Affected Software

16 affected componentsFixes available
maven/org.apache.activemq:activemq-web>=6.0.0<6.2.2
6.2.2
maven/org.apache.activemq:activemq-web<5.19.3
5.19.3
maven/org.apache.activemq:activemq-all>=6.0.0<6.2.2
6.2.2
maven/org.apache.activemq:activemq-all<5.19.3
5.19.3
maven/org.apache.activemq:activemq-broker>=6.0.0<6.2.2
6.2.2
maven/org.apache.activemq:activemq-broker<5.19.3
5.19.3
maven/org.apache.activemq:activemq-client>=6.0.0<6.2.2
6.2.2
maven/org.apache.activemq:activemq-client<5.19.3
5.19.3
Apache ActiveMQ<5.19.3
Apache ActiveMQ>=6.0.0<6.2.2
Apache ActiveMQ Broker<5.19.3
Apache ActiveMQ Broker>=6.0.0<6.2.2
Apache ActiveMQ Web<5.19.3
Apache ActiveMQ Web>=6.0.0<6.2.2
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.7.2.1 - 9.7.2.11
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.6.1.1 - 9.6.1.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.activemq:activemq-web to a version that resolves this vulnerability.

    Fixed in 6.2.2
  2. Upgrade

    Upgrade maven/org.apache.activemq:activemq-web to a version that resolves this vulnerability.

    Fixed in 5.19.3
  3. Upgrade

    Upgrade maven/org.apache.activemq:activemq-all to a version that resolves this vulnerability.

    Fixed in 6.2.2
  4. Upgrade

    Upgrade maven/org.apache.activemq:activemq-all to a version that resolves this vulnerability.

    Fixed in 5.19.3
  5. Upgrade

    Upgrade maven/org.apache.activemq:activemq-broker to a version that resolves this vulnerability.

    Fixed in 6.2.2
  6. Upgrade

    Upgrade maven/org.apache.activemq:activemq-broker to a version that resolves this vulnerability.

    Fixed in 5.19.3
  7. Upgrade

    Upgrade maven/org.apache.activemq:activemq-client to a version that resolves this vulnerability.

    Fixed in 6.2.2
  8. Upgrade

    Upgrade maven/org.apache.activemq:activemq-client to a version that resolves this vulnerability.

    Fixed in 5.19.3
  9. Upgrade

    Upgrade Apache ActiveMQ Client to a version that resolves this vulnerability.

    Fixed in 5.19.4
  10. Upgrade

    Upgrade Apache ActiveMQ Broker to a version that resolves this vulnerability.

    Fixed in 5.19.4
  11. Upgrade

    Upgrade Apache ActiveMQ All to a version that resolves this vulnerability.

    Fixed in 5.19.4
  12. Upgrade

    Upgrade Apache ActiveMQ Web to a version that resolves this vulnerability.

    Fixed in 5.19.4
  13. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 5.19.4
  14. Upgrade

    Upgrade Apache ActiveMQ Client to a version that resolves this vulnerability.

    Fixed in 6.2.3
  15. Upgrade

    Upgrade Apache ActiveMQ Broker to a version that resolves this vulnerability.

    Fixed in 6.2.3
  16. Upgrade

    Upgrade Apache ActiveMQ All to a version that resolves this vulnerability.

    Fixed in 6.2.3
  17. Upgrade

    Upgrade Apache ActiveMQ Web to a version that resolves this vulnerability.

    Fixed in 6.2.3
  18. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 6.2.3

Event History

Apr 7, 2026
CVE Published
via MITRE·07:50 AM
Data Sourced
via MITRE·07:50 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 AM
Affected Software
Advisory Published
via GitHub·09:31 AM
Data Sourced
via GitHub·09:31 AM
DescriptionSeverityWeaknessAffected Software
Jul 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203