Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2023-33246: Remote Command Execution in Apache RocketMQ Update Configuration Function

Published May 24, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS96.6%100th percentile
CISA KEVYesAdded Sep 6, 2023
In the wildActivePer CISA KEV
Vendor
Apache Software Foundation
IdentifiersCVE-2023-33246CWE-94 · Improper Control of Generation of…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.

View more in app →
apache_rocketmq_update_config.rbThis repository contains a single Metasploit module: 'apache_rocketmq_update_config.rb', which exploits CVE-2023-33246, a remote code execution vulnerability in Apache RocketMQ versions 5.1.0 and below. The exploit targets the RocketMQ Broker component, which, if exposed to the network and lacking proper authentication, allows attackers to inject arbitrary system commands via the update configuration functionality. The module is weaponized, supporting customizable payloads (defaulting to a Meterpreter reverse shell) and is capable of automatically detecting the target version and broker port. The attack is performed over TCP, typically targeting ports 9876 (NameServer) and 10911 (Broker). The exploit is operational on Unix and Linux platforms. The repository is structured as a single Ruby file compatible with the Metasploit framework, and leverages Metasploit's command stager and auxiliary RocketMQ modules for payload delivery and version detection.Disclosed May 23, 2023 · Framework: metasploit · ruby · networkWeaponizedCVE-2023-33246_RocketMQ_RCE_EXPLOITThis repository provides an operational exploit and detection toolkit for CVE-2023-33246, a remote code execution vulnerability in Apache RocketMQ (versions 5.1.0 and below). The main exploit script, 'CVE-2023-33246_RocketMQ_RCE_EXPLOIT.py', crafts and sends a malicious RocketMQ protocol message to a specified broker IP and port (default 10911), injecting arbitrary system commands via the configuration update mechanism. The exploit is executed over a raw TCP connection and can run any command as the RocketMQ service user. The repository also includes 'check.py', a multi-threaded scanner that can check single IPs, files of targets, or CIDR ranges for vulnerable RocketMQ instances, defaulting to port 9876 (nameserver) but configurable. The README provides detailed usage instructions, detection guidance, and mitigation advice. No hardcoded C2 or external endpoints are present in the code, but the exploit is capable of executing arbitrary commands, including those that may reach out to attacker-controlled infrastructure. The repository is structured for both exploitation and detection, with clear separation between the exploit and scanning logic.Malayke · Disclosed Jun 1, 2023 · python · networkOperationalCVE-2023-33246This repository is a proof-of-concept exploit for CVE-2023-33246, targeting Apache RocketMQ (version 4.9.1 as per the Maven dependency). The main exploit logic is implemented in 'src/main/java/org/example/Main.java'. The exploit attempts to update the configuration of RocketMQ brokers at three hardcoded IP addresses by injecting a malicious value into the 'rocketmqHome' property. The payload is designed to execute a shell command on the target, which pings a unique domain (chr17sz2vtc0000ymdaggehyuhhyyyyyb.oast.fun) for out-of-band detection of successful command execution. The repository includes standard Java project files and Maven configuration, with the exploit code as the main entry point. No framework is used; this is a standalone Java POC. The attack vector is network-based, requiring access to the RocketMQ broker's management interface.I5N0rth · Disclosed May 30, 2023 · java · xml · networkPoC
Exposure surface

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.

VendorProductType
Apache Software FoundationRocketmqapplication
FAQ

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.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+6 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware10Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.