# CVE-2023-46604: Apache ActiveMQ Deserialization of Untrusted Data > Remote attackers can execute arbitrary code on Apache ActiveMQ brokers or clients by manipulating serialized class types in the OpenWire protocol. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H`) - **Exploited in the wild:** Yes, since 2 Nov 2023 (CISA KEV), used in ransomware - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Oct 2023 - **Updated:** 3 Nov 2025 - **Also known as:** BIT-activemq-2023-46604, DEBIAN-CVE-2023-46604, GHSA-crg9-44h2-xw35, OESA-2023-1778, ROOT-APP-MAVEN-CVE-2023-46604, UBUNTU-CVE-2023-46604 ## What is CVE-2023-46604? CVE-2023-46604 is a critical unsafe deserialization vulnerability in Apache Activemq, published on 27 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The Java OpenWire protocol marshaller is vulnerable to Remote Code Execution. This vulnerability may allow a remote attacker with network access to either a Java-based OpenWire broker or client to run arbitrary shell commands by manipulating serialized class types in the OpenWire protocol to cause either the client or the broker (respectively) to instantiate any class on the classpath. Users are recommended to upgrade both brokers and clients to version 5.15.16, 5.16.7, 5.17.6, or 5.18.3 which fixes this issue. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2023-46604? 17 open source packages ship an affected version, including org.apache.activemq:activemq-client, activemq and org.apache.activemq:activemq-openwire-legacy. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.activemq:activemq-client` | Maven | All versions | 5.15.16 | | `org.apache.activemq:activemq-client` | Maven | All versions | 5.15.16 | | `org.apache.activemq:activemq-client` | Maven | From 5.16.0 | 5.16.7 | | `org.apache.activemq:activemq-client` | Maven | From 5.16.0 | 5.16.7 | | `org.apache.activemq:activemq-client` | Maven | From 5.17.0 | 5.17.6 | | `org.apache.activemq:activemq-client` | Maven | From 5.17.0 | 5.17.6 | | `org.apache.activemq:activemq-client` | Maven | From 5.18.0 | 5.18.3 | | `org.apache.activemq:activemq-client` | Maven | From 5.18.0 | 5.18.3 | | `activemq` | Bitnami | All versions | 5.15.16, 5.16.7, 5.17.6, 5.18.3 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.16.0 | 5.16.7 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.16.0 | 5.16.7 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.17.0 | 5.17.6 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.17.0 | 5.17.6 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.18.0 | 5.18.3 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.18.0 | 5.18.3 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.8.0 | 5.15.16 | | `org.apache.activemq:activemq-openwire-legacy` | Maven | From 5.8.0 | 5.15.16 | Products: Apache Activemq, Apache Activemq Legacy Openwire Module, Debian Debian Linux, Netapp E-Series Santricity Unified Manager, Netapp E-Series Santricity Web Services Proxy, Netapp Santricity Storage Plugin. ## How do I fix CVE-2023-46604? Upgrade org.apache.activemq:activemq-client to a fixed version for your release line: 5.15.16, 5.16.7, 5.17.6 or 5.18.3. US federal agencies must fix it by 23 Nov 2023. ## Is CVE-2023-46604 being exploited? Yes. Attackers have exploited CVE-2023-46604 in the wild since at least 2 Nov 2023, including in ransomware campaigns. Public exploit code: - Achieving a Reverse Shell Exploit for Apache ActiveMQ (CVE_2023-46604) (github_poc): https://github.com/SaumyajeetDas/CVE-2023-46604-RCE-Reverse-Shell-Apache-ActiveMQ - Apache ActiveMQ漏洞综合利用工具(CVE-2015-5254，CVE-2016-3088，CVE-2022-41678，CVE-2023-46604，CVE-2024-32114，CVE-2026-34197，CVE-2026-40466， CVE-2026-42588) (github_poc): https://github.com/Catherines77/ActiveMQ-EXPtools - ActiveMQ RCE (CVE-2023-46604) 回显利用工具 (github_poc): https://github.com/Arlenhiack/ActiveMQ-RCE-Exploit - https://github.com/evkl1d/CVE-2023-46604 (github_poc): https://github.com/evkl1d/CVE-2023-46604 - CVE-2023-46604 (github_poc): https://github.com/trganda/ActiveMQ-RCE - This script leverages CVE-2023046604 (Apache ActiveMQ) to generate a pseudo shell. The vulnerability allows for remote code execution due to unsafe deserialization within the OpenWire protocol. (github_poc): https://github.com/duck-sec/CVE-2023-46604-ActiveMQ-RCE-pseudoshell ## Other vulnerabilities in Apache Activemq - [CVE-2016-3088](https://insights.sbomify.com/CVE-2016-3088/): Apache ActiveMQ Improper Input Validation (critical 9.8, exploited in the wild) - [CVE-2026-34197](https://insights.sbomify.com/CVE-2026-34197/): Apache ActiveMQ Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2020-11998](https://insights.sbomify.com/CVE-2020-11998/): Remote code execution in Apache ActiveMQ (critical 9.8) - [CVE-2013-7285](https://insights.sbomify.com/CVE-2013-7285/): Command Injection in Xstream (critical 9.8) - [CVE-2014-3600](https://insights.sbomify.com/CVE-2014-3600/): Improper Restriction of XML External Entity Reference in Apache ActiveMQ (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-46604 and fix it if it is affected. What it is: CVE-2023-46604 is a critical unsafe deserialization vulnerability in Apache Activemq, published on 27 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2023-46604 in the wild since at least 2 Nov 2023, including in ransomware campaigns. Affected packages and fixed versions: - org.apache.activemq:activemq-client (Maven): affected all versions; fixed in 5.15.16 - org.apache.activemq:activemq-client (Maven): affected all versions; fixed in 5.15.16 - org.apache.activemq:activemq-client (Maven): affected from 5.16.0; fixed in 5.16.7 - org.apache.activemq:activemq-client (Maven): affected from 5.16.0; fixed in 5.16.7 - org.apache.activemq:activemq-client (Maven): affected from 5.17.0; fixed in 5.17.6 - org.apache.activemq:activemq-client (Maven): affected from 5.17.0; fixed in 5.17.6 - org.apache.activemq:activemq-client (Maven): affected from 5.18.0; fixed in 5.18.3 - org.apache.activemq:activemq-client (Maven): affected from 5.18.0; fixed in 5.18.3 - activemq (Bitnami): affected all versions; fixed in 5.15.16, 5.16.7, 5.17.6, 5.18.3 - org.apache.activemq:activemq-openwire-legacy (Maven): affected from 5.16.0; fixed in 5.16.7 - org.apache.activemq:activemq-openwire-legacy (Maven): affected from 5.16.0; fixed in 5.16.7 - org.apache.activemq:activemq-openwire-legacy (Maven): affected from 5.17.0; fixed in 5.17.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-46604/ (Markdown: https://insights.sbomify.com/CVE-2023-46604/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46604 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46604 - OSV: https://osv.dev/vulnerability/CVE-2023-46604 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-46604/ Summaries are generated and may contain mistakes; the official description above is the record.