How severe is GHSA-5x3v-2gxr-59m2?

No CVSS score has been assigned to GHSA-5x3v-2gxr-59m2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5x3v-2gxr-59m2?

GHSA-5x3v-2gxr-59m2 affects the following packages: org.apache.rocketmq:rocketmq-broker (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5x3v-2gxr-59m2?

Update org.apache.rocketmq:rocketmq-broker to 4.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5x3v-2gxr-59m2 is resolved across your whole dependency graph.

How do I detect GHSA-5x3v-2gxr-59m2 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rocketmq:rocketmq-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5x3v-2gxr-59m2 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-5x3v-2gxr-59m2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5x3v-2gxr-59m2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5x3v-2gxr-59m2?

GHSA-5x3v-2gxr-59m2 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5x3v-2gxr-59m2?

GHSA-5x3v-2gxr-59m2 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-5x3v-2gxr-59m2 published, and has it been updated?

GHSA-5x3v-2gxr-59m2 was published on July 1, 2020 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Directory traversal in Apache RocketMQ

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.rocketmq:rocketmq-broker

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

In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.rocketmq:rocketmq-broker`	≥ 4.2.0&&< 4.6.1	4.6.1`org.apache.rocketmq:rocketmq-broker:4.6.1`

Affected Products

1 product · 1 configurations

Application

rocketmqapache

≥ 4.2.0 && ≤ 4.6.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rocketmq:rocketmq-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.rocketmq:rocketmq-broker to 4.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5x3v-2gxr-59m2 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-5x3v-2gxr-59m2 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Directory traversal in Apache RocketMQGHSA-5x3v-2gxr-59m2