Skip to main content
Exploitation reportedNot in CISA KEV yetFix available

CVE-2024-32114

Exploitation reported by one source. First attested on 2026-04-17 by GCVE · kevintel.

  • Published2024-05-02
  • Fixed in6.1.2
  • WeaknessCWE-1188

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping">   <property name="constraint" ref="securityConstraint" />   <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.

Timeline

dates in UTC
  1. 2024-05-0209:15CVE publishedNVD
  2. 2026-04-1718:30Listed as exploited by GCVEGCVE
  3. 2026-04-1718:30Exploitation first reportedGCVE
  4. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-32114?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-32114?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP
Apache activemq
BranchAffectedFixed in
6.x≥ 6.0.0, < 6.1.26.1.2
6.x= 6.xno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Apache activemq to 6.1.2

Advisories and patches

Detection

read 2026-10-23 19:24 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedCatherines77/ActiveMQ-EXPtools
PoC-in-GitHub

Sources

  • GCVEexploitation2026-04-17
  • CISA-ADPSSVC decisionnone2024-05-02
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.18.5read 2026-10-23
  • NVDCVSS 3.18.8read 2026-10-23
  • CNAweakness (CWE)CWE-1188read 2026-10-23
  • FIRST EPSSEPSS score7.1 %2026-10-22
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2024-05-02
Last Modified
2026-06-17
NVD status
Analyzed

Frequently asked questions

What is CVE-2024-32114?

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: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping">   <property name="constraint" ref="securityConstraint" />   <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.

Is CVE-2024-32114 actively exploited?

Active exploitation of CVE-2024-32114 has not been confirmed. Its EPSS score was 7.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-32114?

CVE-2024-32114 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month