CVE-2023-33246: Remote Command Execution in Apache RocketMQ Update Configuration Function
- Vendor
- Apache Software Foundation
CVE-2023-33246 is a remote command execution vulnerability affecting Apache RocketMQ 5.1.0 and earlier, with related affected 4.x releases addressed in later maintenance updates. Under certain deployment conditions, RocketMQ administrative components including NameServer, Broker, and Controller may be reachable from external networks without effective permission verification. An unauthenticated attacker can abuse the update configuration function, or craft RocketMQ protocol content to achieve the same result, to inject configuration values that are later interpreted in a way that results in operating system command execution. In observed exploitation analyses, attackers modified broker configuration fields to trigger shell execution paths and run arbitrary commands as the operating system account used by the RocketMQ service.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote unauthenticated command execution on exposed RocketMQ instances. Commands run with the privileges of the RocketMQ service account, enabling attackers to download and execute additional payloads, establish persistence, deploy malware such as botnets or cryptominers, perform follow-on reconnaissance and lateral movement, and compromise the confidentiality, integrity, and availability of the affected host and potentially adjacent systems.
Mitigation
If you can’t patch tonight, do this now.
Do not expose RocketMQ administrative components such as NameServer, Broker, and Controller to the internet or untrusted networks. Enforce network-level access restrictions so only trusted administrative hosts can reach RocketMQ management interfaces and protocol endpoints. Where possible, ensure permission verification and administrative access controls are enabled and validated. Monitor RocketMQ configuration changes and suspicious child-process execution from RocketMQ service processes, and investigate for historical compromise because patching alone does not remove attacker persistence if exploitation has already occurred.
Remediation
Patch, then assume compromise.
Upgrade Apache RocketMQ to a fixed release. For RocketMQ 5.x, upgrade to 5.1.1 or later for CVE-2023-33246 remediation. For RocketMQ 4.x, upgrade to 4.9.6 or later. Because later reporting identified the original fix as incomplete for the NameServer component, environments using exposed NameServer functionality should further upgrade NameServer to 5.1.2 or later on RocketMQ 5.x, or 4.9.7 or later on RocketMQ 4.x, to address the follow-on issue tracked as CVE-2023-37582.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2023-33246 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 6, 2023.
- Is there a public exploit for CVE-2023-33246?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2023-33246, the earliest disclosed May 23, 2023.
- Is there a patch for CVE-2023-33246?
- Upgrade Apache RocketMQ to a fixed release. For RocketMQ 5.x, upgrade to 5.1.1 or later for CVE-2023-33246 remediation.
- What products are affected by CVE-2023-33246?
- Apache Software Foundation Rocketmq.
- How severe is CVE-2023-33246?
- CVE-2023-33246 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 96.6% (100th percentile) as of Oct 16, 2026.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.