dbcve.org
ActivemqApplication · Apache

CVE-2026-49270

MEDIUM · 5.9 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: 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; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 6.2.6 or 5.19.7, 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

Sensitive information exposure in Apache ActiveMQ allows unauthenticated attackers to retrieve metadata about durable topic subscriptions (client IDs, subscription names, destinations, JMS selectors) by sending a BrokerInfo command to brokers with syncDurableSubs=true, without the broker verifying authentication first.

MitigationUpgrade to Apache ActiveMQ 5.19.7 or 6.2.6, or temporarily disable syncDurableSubs on network connectors if immediate upgrade is not possible.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check ActiveMQ version
    Locate the ActiveMQ installation and run the version command (bin/activemq --version) or read the VERSION file in the installation directory
    Affected if The installed version is below 5.19.7, or is 6.0.0 through 6.2.5 (inclusive)
  2. Identify network connector configurations
    Inspect the ActiveMQ broker XML configuration file (typically conf/activemq.xml or conf/broker-config.xml) and search for <networkConnector> elements
    Affected if Any networkConnector element has the attribute syncDurableSubs set to true
  3. Verify broker authentication is enabled
    Examine the same broker XML configuration file for authentication plugins such as <simpleAuthenticationPlugin>, <jaasAuthenticationPlugin>, or other authentication mechanisms within the <plugins> or <broker> section
    Affected if No authentication plugin is configured, or authentication is present but is not applied to the BrokerInfo command handling (the broker accepts unauthenticated BrokerInfo requests)
  4. Confirm BrokerInfo exposure
    From an external system, attempt to send a BrokerInfo command to the affected broker port (default 61616 for OpenWire) without providing credentials and observe if a response containing durable subscription details is returned
    Affected if The broker responds with subscription metadata (client IDs, subscription names, topics, selectors) without requiring authentication

You are affected if your ActiveMQ version is in the vulnerable range and you have network connectors with syncDurableSubs=true enabled without proper authentication protection on BrokerInfo commands.

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 5.19.7 or 6.2.6, or temporarily disable syncDurableSubs on network connectors if immediate upgrade is not possible.

Recommended fix High confidence

6.2.6 (preferred) or 5.19.7

  1. 1. Review the current Apache ActiveMQ version by checking the installation directory or running `activemq --version`
  2. 2. Back up the current ActiveMQ configuration files (activemq.xml, login.config, and any custom configurations)
  3. 3. Download the recommended fixed version (6.2.6 for the latest stable release, or 5.19.7 for the 5.x branch) from the official Apache ActiveMQ download page at https://activemq.apache.org/download
  4. 4. Stop the ActiveMQ broker gracefully using `./activemq stop` or the equivalent service command
  5. 5. Install the new version by extracting the downloaded archive to the desired location
  6. 6. Restore the backed-up configuration files to the new installation
  7. 7. Review the release notes for the new version to check for any configuration changes needed
  8. 8. Start the ActiveMQ broker using `./activemq start` or the equivalent service command
Caveat Standard upgrade precautions apply - review release notes and test in non-production environment before deploying to production

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

Fix this in Activemq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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