{"id":"CVE-2025-66168","aliases":["BIT-activemq-2025-66168","DEBIAN-CVE-2025-66168","EUVD-2025-208266","GHSA-c825-6ph3-4h84","OESA-2026-1607","OESA-2026-1608","OESA-2026-1609","OESA-2026-1610","OESA-2026-1611","OESA-2026-1679","OESA-2026-1680","OESA-2026-1681","ROOT-APP-MAVEN-CVE-2025-66168","UBUNTU-CVE-2025-66168"],"status":"published","title":"Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","severity":{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00872,"percentile":0.59356,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-190"],"published":"2026-03-04T08:45:00Z","modified":"2026-10-28T20:16:38Z","fixes":[{"ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","fixed_in":["5.19.2","6.1.9","6.2.1"],"sources":["ghsa","osv"]},{"ecosystem":"Maven","package":"org.apache.activemq:activemq-all","fixed_in":["5.19.2","6.1.9","6.2.1"],"sources":["ghsa","osv"]},{"ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","fixed_in":["5.19.2","6.1.9","6.2.1"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"activemq","fixed_in":["5.19.2","6.1.9","6.2.1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP1","package":"activemq","fixed_in":["5.19.2-1.oe2403sp1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP2","package":"activemq","fixed_in":["5.19.2-1.oe2403sp2"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP3","package":"activemq","fixed_in":["5.19.2-1.oe2403sp3"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP4","package":"activemq","fixed_in":["5.19.2-1.oe2203sp4"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS","package":"activemq","fixed_in":["5.19.2-1.oe2403"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"io.root.org.apache.activemq:activemq-mqtt","fixed_in":["5.18.3-root.io.1","6.1.3-root.io.2","6.1.3-root.io.3","5.18.3-root.io.8","6.1.3-root.io.4","5.18.3-root.io.9","5.18.3-root.io.10","6.1.3-root.io.5","5.18.3-root.io.11","6.1.3-root.io.6","6.1.3-root.io.7","5.18.3-root.io.12","6.1.3-root.io.8"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"io.root.org.apache.activemq:activemq-all","fixed_in":["6.1.3-root.io.2","6.1.3-root.io.3","6.1.3-root.io.4","6.1.3-root.io.5","6.1.3-root.io.6","6.1.3-root.io.7","6.1.3-root.io.8"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"org.apache.activemq:activemq-mqtt","fixed_in":["5.18.3-aikido.10","6.1.3-aikido.5","5.18.3-aikido.11","6.1.3-aikido.6","6.1.3-aikido.7","5.18.3-aikido.12","6.1.3-aikido.8"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"org.apache.activemq:activemq-all","fixed_in":["6.1.3-aikido.5","6.1.3-aikido.6","6.1.3-aikido.7","6.1.3-aikido.8"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"last_affected":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"last_affected":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"last_affected":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"osv","ecosystem":"Bitnami","package":"activemq","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.19.2"},{"introduced":"6.0.0"},{"fixed":"6.1.9"},{"introduced":"6.2.0"},{"fixed":"6.2.1"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.2+dfsg-2","5.17.2+dfsg-2+deb12u1","5.17.6+dfsg-1","5.17.6+dfsg-2"]},{"source":"osv","ecosystem":"Debian:13","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.6+dfsg-2"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}],"versions":["4.1.1","4.1.2","5.0.0","5.1.0","5.10.0","5.10.1","5.10.2","5.11.0","5.11.1","5.11.2","5.11.3","5.11.4","5.12.0","5.12.1","5.12.2","5.12.3","5.13.0","5.13.1","5.13.2","5.13.3","5.13.4","5.13.5","5.14.0","5.14.1","5.14.2","5.14.3","5.14.4","5.14.5","5.15.0","5.15.1","5.15.10","5.15.11","5.15.12","5.15.13","5.15.14","5.15.15","5.15.16","5.15.2","5.15.3","5.15.4","5.15.5","5.15.6","5.15.7","5.15.8","5.15.9","5.16.0","5.16.1","5.16.2","5.16.3","5.16.4","5.16.5","5.16.6","5.16.7","5.16.8","5.17.0","5.17.1","5.17.2","5.17.3","5.17.4","5.17.5","5.17.6","5.17.7","5.18.0","5.18.1","5.18.2","5.18.3","5.18.4","5.18.5","5.18.6","5.18.7","5.19.0","5.19.1","5.2.0","5.3.0","5.3.1","5.3.2","5.4.0","5.4.1","5.4.2","5.4.3","5.5.0","5.5.1","5.6.0","5.7.0","5.8.0","5.9.0","5.9.1"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}],"versions":["6.0.0","6.0.1","6.1.0","6.1.1","6.1.2","6.1.3","6.1.4","6.1.5","6.1.6","6.1.7","6.1.8"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}],"versions":["4.1.2","5.0.0","5.1.0","5.10.0","5.10.1","5.10.2","5.11.0","5.11.1","5.11.2","5.11.3","5.11.4","5.12.0","5.12.1","5.12.2","5.12.3","5.13.0","5.13.1","5.13.2","5.13.3","5.13.4","5.13.5","5.14.0","5.14.1","5.14.2","5.14.3","5.14.4","5.14.5","5.15.0","5.15.1","5.15.10","5.15.11","5.15.12","5.15.13","5.15.14","5.15.15","5.15.16","5.15.2","5.15.3","5.15.4","5.15.5","5.15.6","5.15.7","5.15.8","5.15.9","5.16.0","5.16.1","5.16.2","5.16.3","5.16.4","5.16.5","5.16.6","5.16.7","5.16.8","5.17.0","5.17.1","5.17.2","5.17.3","5.17.4","5.17.5","5.17.6","5.17.7","5.18.0","5.18.1","5.18.2","5.18.3","5.18.4","5.18.5","5.18.6","5.18.7","5.19.0","5.19.1","5.2.0","5.3.0","5.3.1","5.3.2","5.4.0","5.4.1","5.4.2","5.4.3","5.5.0","5.5.1","5.6.0","5.7.0","5.8.0","5.9.0","5.9.1"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}],"versions":["6.0.0","6.0.1","6.1.0","6.1.1","6.1.2","6.1.3","6.1.4","6.1.5","6.1.6","6.1.7","6.1.8"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2"}]}],"versions":["5.10.0","5.10.1","5.10.2","5.11.0","5.11.1","5.11.2","5.11.3","5.11.4","5.12.0","5.12.1","5.12.2","5.12.3","5.13.0","5.13.1","5.13.2","5.13.3","5.13.4","5.13.5","5.14.0","5.14.1","5.14.2","5.14.3","5.14.4","5.14.5","5.15.0","5.15.1","5.15.10","5.15.11","5.15.12","5.15.13","5.15.14","5.15.15","5.15.16","5.15.2","5.15.3","5.15.4","5.15.5","5.15.6","5.15.7","5.15.8","5.15.9","5.16.0","5.16.1","5.16.2","5.16.3","5.16.4","5.16.5","5.16.6","5.16.7","5.16.8","5.17.0","5.17.1","5.17.2","5.17.3","5.17.4","5.17.5","5.17.6","5.17.7","5.18.0","5.18.1","5.18.2","5.18.3","5.18.4","5.18.5","5.18.6","5.18.7","5.19.0","5.19.1","5.8.0","5.9.0","5.9.1"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}],"versions":["6.0.0","6.0.1","6.1.0","6.1.1","6.1.2","6.1.3","6.1.4","6.1.5","6.1.6","6.1.7","6.1.8"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.2.1"}]}],"versions":["6.2.0"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403sp1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403sp2"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403sp3"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2203sp4"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2403sp3"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.2-1.oe2203sp4"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"io.root.org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.18.3-root.io.1"},{"fixed":"6.1.3-root.io.2"},{"fixed":"6.1.3-root.io.3"},{"fixed":"5.18.3-root.io.8"},{"fixed":"6.1.3-root.io.4"},{"fixed":"5.18.3-root.io.9"},{"fixed":"5.18.3-root.io.10"},{"fixed":"6.1.3-root.io.5"},{"fixed":"5.18.3-root.io.11"},{"fixed":"6.1.3-root.io.6"},{"fixed":"6.1.3-root.io.7"},{"fixed":"5.18.3-root.io.12"},{"fixed":"6.1.3-root.io.8"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"io.root.org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.3-root.io.2"},{"fixed":"6.1.3-root.io.3"},{"fixed":"6.1.3-root.io.4"},{"fixed":"6.1.3-root.io.5"},{"fixed":"6.1.3-root.io.6"},{"fixed":"6.1.3-root.io.7"},{"fixed":"6.1.3-root.io.8"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"org.apache.activemq:activemq-mqtt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.18.3-aikido.10"},{"fixed":"6.1.3-aikido.5"},{"fixed":"5.18.3-aikido.11"},{"fixed":"6.1.3-aikido.6"},{"fixed":"6.1.3-aikido.7"},{"fixed":"5.18.3-aikido.12"},{"fixed":"6.1.3-aikido.8"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"org.apache.activemq:activemq-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.3-aikido.5"},{"fixed":"6.1.3-aikido.6"},{"fixed":"6.1.3-aikido.7"},{"fixed":"6.1.3-aikido.8"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0+dfsg1-4+deb8u1ubuntu1","5.6.0+dfsg1-5","5.13.2+dfsg-2","5.13.2+dfsg-2ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.5-3","5.15.2-2","5.15.3-2","5.15.8-2~18.04","5.15.8-2~18.04.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.10-1","5.15.11-1","5.15.11-1ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.16.1-1","5.16.1-1ubuntu0.1~esm1","5.16.1-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.2+dfsg-2","5.17.6+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.6+dfsg-1","5.17.6+dfsg-2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.6+dfsg-2","5.17.6+dfsg-2ubuntu1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.6+dfsg-2"]}],"products":[{"vendor":"apache","product":"activemq"},{"vendor":"apache software foundation","product":"apache activemq"},{"vendor":"apache software foundation","product":"apache activemq all module"},{"vendor":"apache software foundation","product":"apache activemq mqtt module"}],"references":[{"url":"https://lists.apache.org/thread/13n8mkrb2jf2y6yyhpgrkmpqcm7djyto","tags":["vendor-advisory","Mailing List","Vendor Advisory","advisory","web","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-40046","tags":["related","web"]},{"url":"https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt","tags":["related","web","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2026/03/03/5","tags":["Mailing List","Third Party Advisory","advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-66168","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-c825-6ph3-4h84"},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/66xxx/CVE-2025-66168.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-66168","tags":["advisory"]},{"url":"https://github.com/apache/activemq","tags":["package"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1607","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1608","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1609","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1610","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1611","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1679","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1680","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1681","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-66168","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-66168","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-66168","title":"Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T08:45:00.932Z","modified":"2026-04-10T10:52:27.564Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-190"],"updated_at":"2026-11-02T14:32:53.157279Z"}],"euvd":[{"id":"EUVD-2025-208266","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T08:45:00Z","modified":"2026-04-10T10:52:27Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T19:24:30.341772Z"}],"ghsa":[{"id":"GHSA-c825-6ph3-4h84","title":"Apache ActiveMQ is Vulnerable to Integer Overflow or Wraparound","description":"Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T09:31:07Z","modified":"2026-04-10T14:59:48Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-190"],"updated_at":"2026-11-02T14:39:52.102227Z"}],"nvd":[{"id":"CVE-2025-66168","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T09:15:54.757Z","modified":"2026-06-17T09:56:26.157Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-190"],"updated_at":"2026-11-02T14:12:01.096037Z"}],"osv":[{"id":"CVE-2025-66168","title":"Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T08:45:00.932Z","modified":"2026-10-28T02:30:44.417384818Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-190"],"updated_at":"2026-11-02T15:44:52.202386Z"},{"id":"DEBIAN-CVE-2025-66168","description":"WARNING:  Users of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.  See the  following for more details:  https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt   https://www.cve.org/CVERecord?id=CVE-2026-40046     Original Report:  Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.  This issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0  Users are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T09:15:54.757Z","modified":"2026-09-01T20:05:56.083120951Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:47.697959Z"},{"id":"GHSA-c825-6ph3-4h84","title":"Apache ActiveMQ is Vulnerable to Integer Overflow or Wraparound","description":"Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T09:31:07Z","modified":"2026-09-10T03:50:38.840053597Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-190"],"updated_at":"2026-11-02T15:46:44.927642Z"},{"id":"OESA-2026-1607","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-15T11:10:37Z","modified":"2026-08-18T01:19:37.819466202Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1608","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-15T11:10:37Z","modified":"2026-08-18T01:19:37.895442566Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1609","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-15T07:31:18Z","modified":"2026-08-18T01:19:40.318449814Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1610","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-15T07:31:20Z","modified":"2026-08-18T01:19:40.339574018Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1611","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-15T07:31:22Z","modified":"2026-08-18T01:19:38.002963633Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1679","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-20T11:10:42Z","modified":"2026-08-18T01:19:41.548828807Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1680","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-20T11:10:42Z","modified":"2026-08-18T01:19:41.711235192Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1681","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\n\nA vulnerability classified as problematic has been found in Apache ActiveMQ (Application Server Software).CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.This is going to have an impact on integrity, and availability.Upgrading to version 5.19.2, 6.1.9 or 6.2.1 eliminates this vulnerability.(CVE-2025-66168)","status":"published","published":"2026-03-20T11:10:42Z","modified":"2026-08-18T01:19:41.663942185Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"UBUNTU-CVE-2025-66168","description":"WARNING: Users of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases. See the  following for more details: https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt  https://www.cve.org/CVERecord?id=CVE-2026-40046 Original Report: Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted. This issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0 Users are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-04T09:15:00Z","modified":"2026-10-28T20:16:38.121771843Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"},{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:55:52.345622Z"},{"id":"BIT-activemq-2025-66168","title":"Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated","description":"WARNING:\n\nUsers of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.\n\nSee the  following for more details:\n https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt \n https://www.cve.org/CVERecord?id=CVE-2026-40046 \n\n\n\nOriginal Report:\n\nApache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.\n\nThis issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0\n\nUsers are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.","status":"published","published":"2026-03-06T08:36:37.326Z","modified":"2026-09-08T08:45:07.712413576Z","updated_at":"2026-11-02T15:28:28.267217Z"},{"id":"ROOT-APP-MAVEN-CVE-2025-66168","title":"CVE-2025-66168 in io.root.org.apache.activemq:activemq-mqtt - Patched by Root","description":"Root has patched CVE-2025-66168 in the io.root.org.apache.activemq:activemq-mqtt package for Root:Maven. Multiple fixed versions available.","status":"published","published":"2026-07-21T07:51:11Z","modified":"2026-07-21T12:15:12.513478559Z","updated_at":"2026-11-02T15:53:27.066589Z"}]}}