dbcve.org
ActivemqApplication · Apache

CVE-2026-50750

HIGH · 7.5 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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
Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM. This issue affects Apache ActiveMQ Broker: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ All: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7. Users are recommended to upgrade to version 6.2.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

An unauthenticated attacker can cause an Apache ActiveMQ broker to crash via out-of-memory (OOM) by sending repeated BrokerInfo commands without first sending a ConnectionInfo command. This vulnerability bypasses a previous fix (CVE-2026-49270) and allows memory exhaustion on the broker.

MitigationUpgrade Apache ActiveMQ to version 5.19.8 or 6.2.7 (depending on the product line) to patch this vulnerability. Consider implementing network-level access controls to limit exposure to unauthenticated attackers.

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.2.6
Activemq BrokerApplication
Affected:= 5.19.7= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed Apache ActiveMQ version
    Run the command `activemq --version` or check the version file in the ActiveMQ installation directory (such as `bin/activemq` version output or `lib/activemq-core-*` jar file name)
    Affected if The installed version is exactly 5.19.7 or exactly 6.2.6, as these are the only versions listed as affected
  2. Verify broker network exposure
    Review network configuration to determine if the ActiveMQ broker port (default 61616) is accessible from untrusted networks or the public internet
    Affected if The broker is reachable by unauthenticated attackers over the network, as the vulnerability is exploitable without any credentials
  3. Confirm OpenWire protocol is enabled
    Check the ActiveMQ configuration file (typically `conf/activemq.xml`) for an OpenWire transport connector binding to a network interface accessible externally
    Affected if An OpenWire transport connector is bound to a non-localhost interface (0.0.0.0 or external IP), allowing remote connections without authentication

You are affected if your ActiveMQ installation is version 5.19.7 or 6.2.6 AND the broker is accessible over the network to unauthenticated users, since the exploit requires sending BrokerInfo commands without prior ConnectionInfo authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache ActiveMQ to version 5.19.8 or 6.2.7 (depending on the product line) to patch this vulnerability. Consider implementing network-level access controls to limit exposure to unauthenticated attackers.

Recommended fix High confidence

6.2.7 (or 5.19.8 for the 5.x branch)

  1. 1. Identify the currently running Apache ActiveMQ version using broker logs or process inspection
  2. 2. Stop the ActiveMQ broker gracefully to avoid disrupting active connections
  3. 3. Backup the current ActiveMQ installation directory and any persistent storage (kahadb, leveldb, or database-based stores)
  4. 4. Download Apache ActiveMQ 6.2.7 (or 5.19.8 for the 5.x line) from the official Apache distribution mirrors at https://activemq.apache.org/download.html
  5. 5. Extract the new version to the target installation directory, preserving the original conf/ and data/ directories or migrating configurations as needed
  6. 6. Review and apply any new configuration defaults from the new version if relevant to the BrokerInfo fix
  7. 7. Start the upgraded ActiveMQ broker and verify successful startup via logs
  8. 8. Monitor broker memory usage and verify that repeated BrokerInfo commands without ConnectionInfo no longer cause unbounded memory consumption
Caveat Minimal risk - this is a security patch release; review release notes for any minor behavioral changes between 6.2.6 and 6.2.7

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

Fix this in Activemq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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