ZeroDay Findings
Sign inSign up

Findings

Vulnerability · CVE-2024-32114

Apache ActiveMQ Initialization of a Resource with an Insecure Default

Published Apr 22, 2026 · corrected/updated Apr 22, 2026 · Apache ActiveMQ · evidence confidence very high

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 configura VulnCheck canary evidence.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2024-32114 is a unknown public vulnerability record for Apache ActiveMQ. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether Apache ActiveMQ is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: Apache ActiveMQ. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: EPSS 7.1%. CISA lists it as known exploited. Sources contributing to this record: epss, vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Confirmed in CISA KEV since Apr 22, 2026. Listed in CISA KEV and VulnCheck KEV.

  • Patch and remediation

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

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 22, 2026 · VulnCheck KEV

    Detected

    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 AP

  2. Apr 22, 2026 · CISA KEV

    Known exploited

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

Affected

  • vendor Apache ActiveMQversion unspecified

Sources

  • FIRST EPSSExploitation probabilityCVE-2024-32114

    30-day exploitation probability 7.1%

    first.org
  • VulnCheck KEVConfirmed exploitationCVE-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 bro

    vulncheck.com

References