CASCACascade Atlas

Evidence dossier

CVE-2023-33246

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

84.2–99.2Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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 .

State
PUBLISHED
Published
May 24, 2023
Updated
Oct 21, 2025
Evidence coverage
85%
CISA KEVCatalog member

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

FIRST EPSS96.60%

2026-07-18 · v2026.06.15 · percentile 99.9%

Source stateNo scored conflict

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

apacheoriginal assertion
container

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

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

CVEderivative copy
container

CVE Program Container

CISA KEVoriginal assertion
observed_exploitation

Apache RocketMQ Command Execution Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.966040000000; percentile 0.998770000000

Applicability

Cited product scope

Trace impact →
Apache Software FoundationApache RocketMQ
[{"status": "affected", "version": "0", "versionType": "maven", "lessThanOrEqual": "5.1.0"}]unknown
Unknown vendorUnknown product
cpe:2.3:a:apache:rocketmq:*:*:*:*:*:*:*:*; end excluding 4.9.6supported
Unknown vendorUnknown product
cpe:2.3:a:apache:rocketmq:*:*:*:*:*:*:*:*; start including 5.0.0; end excluding 5.1.1supported

Assessments

CVSS by origin

9.8
nvd@nist.govCVSS 3.1 · role PrimaryCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8
134c704f-9b21-4f2e-91b3-4a467353bcc0CVSS 3.1 · role SecondaryCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8
CISA-ADPCVSS 3.1 · role unknownCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.