Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2023-09-06 — agencies required to remediate by 2023-09-27
Maven

CVE-2023-33246

CRITICAL

Apache RocketMQ: Possible remote code execution vulnerability when using the update configuration function

Also known asGHSA-x3cq-8f32-5f63
Published
May 24, 2023
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
20 known

EPSS Exploitation Probability

via FIRST.org ↗
96.6%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
93.7%94.9%96.1%97.3%94.4%96.6%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
org.apache.rocketmq:rocketmq-brokerorg.apache.rocketmq:rocketmq-namesrvorg.apache.rocketmq:rocketmq-controllerorg.apache.rocketmq:rocketmq-namesrv

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution. 

Several components of RocketMQ, including NameServer, Broker, and Controller, are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function to execute commands as the system users that RocketMQ is running as. Additionally, an attacker can achieve the same effect by forging the RocketMQ protocol content. 

To prevent these attacks, users are recommended to upgrade to version 5.1.1 or above for using RocketMQ 5.x or 4.9.6 or above for using RocketMQ 4.x .

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.rocketmq:rocketmq-broker5.0.0&&< 5.1.15.1.1
Mavenorg.apache.rocketmq:rocketmq-namesrv4.0.0&&< 4.9.64.9.6
Mavenorg.apache.rocketmq:rocketmq-controller5.0.0&&< 5.1.15.1.1
Mavenorg.apache.rocketmq:rocketmq-namesrv5.0.0&&< 5.1.15.1.1
Exploits & PoCs
20

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rocketmq:rocketmq-broker. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.rocketmq:rocketmq-broker to 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33246 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-33246 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-33246. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution.  Several components of RocketMQ, including NameServer, Broker, and Controller, are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function to execute commands as the system users that RocketMQ is running as. Additionally, an attacker can achieve the same effect by forging the RocketMQ protocol content.  To prevent these attacks, users are recommended to upgrade to version 5.1.1 or above for using R
O3 Security · Impact-Aware SCA

Is CVE-2023-33246 in your dependencies?

O3 detects CVE-2023-33246 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.