Live › vulnerability › CVE-2023-33246
Go to dashboardApache RocketMQ NameServer, Broker and Controller components lack permission checks and are reachable from the internet. An unauthenticated attacker can run commands as the RocketMQ system user through the update-configuration function, or by forging RocketMQ protocol messages.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| apache rocketmq | vendor | < 4.9.6 | 4.9.6 |
| apache rocketmq | vendor | >= 5.0.0, < 5.1.1 | 5.1.1 |
| Apache RocketMQ | vendor | – | – |
Unknown from the sources.
Apply the mitigations in the Apache RocketMQ vendor advisory or discontinue use of the product if mitigations are unavailable.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 .
This page as .md · .json · in your agent: get_signal("CVE-2023-33246")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.