dbcve.org
ActivemqApplication · Apache

CVE-2026-45505

HIGH · 8.8 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 5.19.7 / 6.2.6 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. Non-parenthesized discovery wrappers such as `masterslave:vm://...,...` and `static:vm://...` incorrectly pass validation allowing bypass of fix in CVE-2026-34197.  Original description from CVE-2026-34197. Apache ActiveMQ exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String). An authenticated attacker can invoke these operations with a crafted discovery UR that triggers 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.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, 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

This CVE is a bypass of CVE-2026-34197. Non-parenthesized discovery wrappers such as `masterslave:vm://...,...` and `static:vm://...` incorrectly pass validation, allowing authenticated attackers to invoke BrokerService operations via the Jolokia JMX-HTTP bridge and load remote Spring XML application contexts for arbitrary code execution.

MitigationUpgrade to Apache ActiveMQ version 5.19.7 or 6.2.6, which includes the fix for this validation bypass.

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.7>= 6.0.0, < 6.2.6
Activemq BrokerApplication
Affected:< 5.19.7>= 6.0.0, < 6.2.6

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 Apache ActiveMQ version
    Check the version of the installed Apache ActiveMQ broker. Common locations: check the 'activemq' or 'activemq-broker' JAR manifest, or run 'activemq --version' from the bin directory, or inspect the 'org/apache/activemq/Version.java' in the JAR.
    Affected if The installed version is less than 5.19.7, or greater than or equal to 6.0.0 but less than 6.2.6.
  2. Determine if Jolokia JMX-HTTP bridge is exposed
    Inspect the ActiveMQ configuration files (typically 'conf/jetty.xml' or 'conf/activemq.xml') for Jolokia servlet or JMX-over-HTTP configuration. Look for 'jolokia' or 'JMXConnector' servlet mappings in the web server configuration.
    Affected if Jolokia JMX-HTTP bridge is enabled and accessible over the network, providing an attacker a vector to invoke MBean methods.
  3. Review network connector configurations for discovery URIs
    Examine the ActiveMQ broker configuration XML (usually 'conf/activemq.xml') for <networkConnector> elements. Inspect the 'uri' or 'discoveryUri' attributes for patterns like 'masterslave:vm://', 'static:vm://', or other discovery protocols.
    Affected if Network connectors use discovery URIs with the 'masterslave:vm://' or 'static:vm://' format without proper validation wrappers.
  4. Review connector configurations for discovery URIs
    Examine the ActiveMQ broker configuration XML for <connector> elements. Inspect any 'uri' attributes that reference discovery protocols, especially 'masterslave:vm://' or 'static:vm://' patterns.
    Affected if Connectors are configured with discovery URIs using the non-parenthesized 'masterslave:vm://' or 'static:vm://' format.
  5. Inspect VM transport brokerConfig usage
    Search the broker configuration for VM transport connectors that use the 'brokerConfig' parameter. Look for URIs containing 'vm://' with 'brokerConfig' set to a Spring XML or property file path.
    Affected if The VM transport is configured with brokerConfig pointing to a remote or controllable XML context file.

You are affected if your ActiveMQ version falls within the vulnerable range AND Jolokia is exposed AND your broker has network/connectors using non-parenthesized discovery URIs like 'masterslave:vm://' or 'static:vm://' with VM transport brokerConfig.

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.7 / 6.2.6 or later
Fixed in 5.19.76.2.6
Interim mitigation

Upgrade to Apache ActiveMQ version 5.19.7 or 6.2.6, which includes the fix for this validation bypass.

Recommended fix High confidence

5.19.7 for 5.x branches; 6.2.6 for 6.x branches

  1. 1. Identify the currently running Apache ActiveMQ version (check bin/activemq --version or the startup logs)
  2. 2. If running version < 5.19.7, plan upgrade to version 5.19.7
  3. 3. If running version >= 6.0.0 and < 6.2.6, plan upgrade to version 6.2.6
  4. 4. Review release notes and migration guides for the target version before upgrading
  5. 5. Test the upgrade in a non-production environment to verify functionality
  6. 6. Create a full backup of the ActiveMQ installation and data directories
  7. 7. Stop the ActiveMQ broker gracefully
  8. 8. Replace the ActiveMQ installation with the new version

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

Fix this in Activemq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45505 — 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-45505 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