CVE-2024-32114
HighExploitedApache ActiveMQ's default configuration doesn't secure the API web context
Published May 2, 2024 · Updated Aug 12, 2026 · Also known as BIT-activemq-2024-32114, GHSA-gj5m-m88j-v7c3
Key Facts
Patch immediately- CVE-2024-32114 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Activemq (Apache), org.apache.activemq:apache-activemq (maven).
- It is exploited in the wild, listed in Industry KEV feed since Apr 22, 2026. No public exploit code is known.
- EPSS estimates a 7.1% probability of exploitation in the next 30 days.
- Fixed versions are available, including Activemq 6.1.2, org.apache.activemq:apache-activemq 6.1.2.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
7.1%
Higher than 94.2% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing
Public exploit code
None known
Get the full CVE-2024-32114 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).
To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:
Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Apr 22, 2026 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
8 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| ActivemqApache | >= 6.0.0 | 6.1.2 |
| org.apache.activemq:apache-activemqmaven | >= 6.0.0 | 6.1.2 |
Patched Releases
Activemq
6.1.2
org.apache.activemq:apache-activemq
6.1.2
Timeline
Publicly disclosed
May 2, 2024
Added to Industry KEV feed
Apr 22, 2026
Last updated
Aug 12, 2026
Weakness Type
- CWE-1188 Initialization of a Resource with an Insecure Default
References
- advisoryhttps://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt
- advisoryGHSA advisory
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2024/32xxx/CVE-2024-32114.json
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2024-32114
- articlehttps://github.com/apache/activemq/commit/43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0
FAQ
Common Questions.
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).
Affected: Activemq (Apache) versions >= 6.0.0; org.apache.activemq:apache-activemq (maven) versions >= 6.0.0. The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since Apr 22, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Activemq 6.1.2, org.apache.activemq:apache-activemq 6.1.2.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2024-32114 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo