Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Remote code execution in Apache ActiveMQGHSA-wqfh-9m4g-7x6x

CRITICALFix: apache/activemq@0d6e5f2

GHSA-wqfh-9m4g-7x6x is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.apache.activemq:activemq-parent. EPSS puts its 30-day exploitation probability at 48.9% (99th percentile). A fix is available for org.apache.activemq:activemq-parent — see the affected versions and patch details below.

Also known asBIT-activemq-2020-11998CVE-2020-11998
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
48.9%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
0.00%21.5%43.0%64.5%6.9%48.9%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-wqfh-9m4g-7x6x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕org.apache.activemq:activemq-parent

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

A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to RMIConnectorServer, instead of the map that contains the authentication credentials, it leaves ActiveMQ open to the following attack: https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html "A remote client could create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs, at least if there is no security manager. In other words, a rogue remote client could make your Java application execute arbitrary code." Mitigation: Upgrade to Apache ActiveMQ 5.15.13

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.activemq:activemq-parent≥ 5.15.12&&< 5.15.135.15.13org.apache.activemq:activemq-parent:5.15.13

Affected Products

7 products · 8 configurations
Application
activemqapache
1 version
5.15.12
Application
communications diameter signaling routeroracle
≥ 8.0.0 && ≤ 8.5.0
range
Application
communications element manageroracle
≥ 8.2.0 && ≤ 8.2.4.0
range
Application
communications session report manageroracle
≥ 8.0.0 && ≤ 8.2.2
range
Application
communications session route manageroracle
≥ 8.0.0 && ≤ 8.2.2
range
Application
enterprise repositoryoracle
1 version
11.1.1.7.0

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.activemq:activemq-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.activemq:activemq-parent to 5.15.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wqfh-9m4g-7x6x 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.

Frequently Asked Questions

A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to RMIConnectorServer, instead of the map that contains the authentication credentials, it leaves ActiveMQ open to the following attack - A remote client could create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs, at least if there is no security manager. In other words, a rogue remote client could make your Java application execute arbitrary code. Mitigation - Upgrade to Apache ActiveMQ 5.15.13
O3 Security · Impact-Aware SCA

Is GHSA-wqfh-9m4g-7x6x in your dependencies?

Find it across Maven, including transitive dependencies.

Remote code execution in Apache ActiveMQ (Critical 9.8)