dbcve.org
ActivemqApplication · Apache

CVE-2026-40466

HIGH · 8.8 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 5.19.6 / 6.2.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. An authenticated attacker may bypass the fix in CVE-2026-34197 by adding a connector using an HTTP Discovery transport via BrokerView.addNetworkConnector or BrokerView.addConnector through Jolokia if the activemq-http module is on the classpath. A malicious HTTP endpoint can return a VM transport through the HTTP URI which will bypass the validation added in CVE-2026-34197. The attacker can then use the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ All: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5. Users are recommended to upgrade to version 5.19.6 or 6.2.5, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated attacker bypasses CVE-2026-34197 fix by using HTTP Discovery transport via Jolokia API to obtain a VM transport, then exploits the brokerConfig parameter to load a remote Spring XML application context (ResourceXmlApplicationContext). Since Spring instantiates singleton beans before BrokerService validation, arbitrary code execution occurs through bean factory methods like Runtime.exec().

MitigationUpgrade Apache ActiveMQ to version 5.19.6 or 6.2.5. If upgrade is not immediately feasible, consider disabling Jolokia or restricting network access to the broker management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ActivemqApplication
Affected:< 5.19.6>= 6.0.0, < 6.2.5
Activemq BrokerApplication
Affected:< 5.19.6>= 6.0.0, < 6.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ActiveMQ version
    Check the installed Apache ActiveMQ version by inspecting the release notes, lib directory, or running a version command if available. Compare against the affected ranges: < 5.19.6 or >= 6.0.0 < 6.2.5
    Affected if The installed version falls within the affected version ranges
  2. Verify Jolokia HTTP management endpoint is exposed
    Check if the Jolokia endpoint is accessible on the ActiveMQ admin console (typically port 8161/admin/jolokia or similar). Inspect the web server configuration for Jolokia servlet mappings
    Affected if The Jolokia REST API is exposed and accessible over the network
  3. Confirm HTTP or HTTP Discovery transport is enabled
    Inspect the ActiveMQ broker configuration (activemq.xml) for transport connectors using HTTP, HTTP Discovery, or failover HTTP protocols
    Affected if HTTP-based transport connectors are defined in the broker configuration
  4. Check for unauthenticated or weak access controls on Jolokia
    Review the authentication configuration for the Jolokia endpoint and admin console. Determine if anonymous access or weak credentials are allowed
    Affected if Jolokia can be accessed without proper authentication or with limited privileges that still permit MBean manipulation
  5. Inspect for suspicious Jolokia MBean operations
    Review broker logs for invocations of JMX operations related to transport configuration, particularly DiscoveryTransport or HTTP discovery-related MBean methods
    Affected if Logs show unusual or unauthorized transport-related MBean operations from remote sources

A user is affected if they run an affected ActiveMQ version with Jolokia HTTP management exposed and HTTP Discovery transport enabled, allowing an authenticated attacker to manipulate transport configuration and load remote malicious Spring XML contexts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.19.6 / 6.2.5 or later
Fixed in 5.19.66.2.5
Interim mitigation

Upgrade Apache ActiveMQ to version 5.19.6 or 6.2.5. If upgrade is not immediately feasible, consider disabling Jolokia or restricting network access to the broker management interfaces.

Recommended fix High confidence

5.19.6 (for 5.x line) or 6.2.5 (for 6.x line)

  1. Identify the current ActiveMQ version by checking the broker startup logs or version file
  2. Stop the ActiveMQ broker service to prevent configuration changes during upgrade
  3. Back up the entire ActiveMQ installation directory, configuration files, and message data
  4. Determine which major version line you are on (5.x or 6.x) to select the appropriate upgrade target
  5. Download the fixed version: 5.19.6 for 5.x users or 6.2.5 for 6.x users from the official Apache ActiveMQ distribution
  6. Extract the new version to a clean directory or replace the existing installation files
  7. Restore your configuration files from the backup (or migrate settings to the new version format if needed)
  8. Start the ActiveMQ broker and verify successful startup
Caveat Review release notes for your target version to check for any configuration or API changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Activemq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40466 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data