{"id":"CVE-2026-33227","summary":"Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ: Improper Limitation of a Pathname to a Restricted Classpath Directory","details":"Improper validation and restriction of a classpath path name vulnerability in \n\n Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ.\n\n\n\nIn 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.\n\n\n\n\n\nThis 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.\n\nUsers 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.","aliases":["BIT-activemq-2026-33227","GHSA-h2h4-5m64-m273"],"modified":"2026-07-15T01:49:12.448933923Z","published":"2026-04-07T07:50:58.897Z","related":["CGA-3gqh-w9c6-v686"],"database_specific":{"unresolved_ranges":[{"source":"AFFECTED_FIELD","extracted_events":[{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"}]},{"extracted_events":[{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"}],"source":"DESCRIPTION"}],"cna_assigner":"apache","cwe_ids":["CWE-22"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33227.json"},"references":[{"type":"WEB","url":"http://www.openwall.com/lists/oss-security/2026/04/06/4"},{"type":"WEB","url":"https://repo.maven.apache.org/maven2"},{"type":"ADVISORY","url":"https://activemq.apache.org/security-advisories.data/CVE-2026-33227-announcement.txt"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33227.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-33227"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/apache/activemq","events":[{"introduced":"0"},{"fixed":"e216f452084ab01641ac5ae8bf7c0d8777c79e9a"},{"introduced":"14bac13f40958c1a1d3d198051eed32facc4abd1"},{"fixed":"ace8c0c4a603bee86baf4785c63e66735e2b8f00"}],"database_specific":{"cpe":"cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*","extracted_events":[{"introduced":"0"},{"fixed":"5.19.3"},{"introduced":"6.0.0"},{"fixed":"6.2.2"}],"source":"CPE_RANGE"}}],"versions":["activemq-6.2.1","activemq-5.19.2","activemq-6.2.0","activemq-5.19.1","activemq-5.19.0","activemq-5.18.6","activemq-5.18.5","activemq-6.1.2","activemq-5.18.4","activemq-6.1.1","activemq-6.1.0","activemq-6.0.0","activemq-5.18.3","activemq-5.18.2","activemq-5.18.1","activemq-5.18.0","activemq-5.16.0","activemq-5.15.0","activemq-5.14.0","activemq-5.13.0","activemq-5.12.0","activemq-5.11.0","activemq-5.10.0","activemq-5.9.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-33227.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"}]}