Skip to main content
← Vulnerabilities

Apache ActiveMQ, ActiveMQ Broker: Repeated rejected temporary destination consumer requests can lead to broker OOM

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.5MediumCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 6.3.3, 5.19.12
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 6.3.3, 5.19.12.

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

CVE-2026-108949 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects Apache ActiveMQ and ActiveMQ Broker; fixed in 6.3.3 and 5.19.12.

Published
Last modified
Published
Not listed in CISA KEV
20/100 · provisional
Fix
Fixed in 6.3.3, 5.19.12
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Apache ActiveMQ and ActiveMQ Broker can be crashed through a denial-of-service flaw: an authenticated OpenWire client that repeatedly sends consumer requests for temporary destinations owned by other connections causes the broker to leak heap memory until it runs out of memory. The leak happens because rejected subscriptions are never cleaned up.

Read the original description

Denial of Service via OOM vulnerability in Apache ActiveMQ, ActiveMQ Broker. An authenticated OpenWire client that sends a ConsumerInfo for a temporary queue/topic owned by another connection is rejected with InvalidDestinationException, but the rejected Subscription is left behind in the region's subscriptions map. Repeating the request leaks broker heap until OOM because the broker does not clean up the rejected subscriptions in the map. This issue affects Apache ActiveMQ: from 6.0.0 before 6.3.3, before 5.19.12; ActiveMQ Broker: from 6.0.0 before 6.3.3, before 5.19.12. Users are recommended to upgrade to version 6.4.0, 6.3.3, or 5.19.12, which fixes the issue.

Impact

  • Widely used

    68 packages depend on org.apache.activemq:activemq-broker.Source: deps.dev

What to do

  • Upgrade to a fixed version: 6.3.3, 5.19.12.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • org.apache.activemq:activemq-brokerMaven

    From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12

  • org.apache.activemq:activemq-brokerMaven

    From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12

Evidence 2

  1. Advisory
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-108949

Is CVE-2026-108949 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-108949?

org.apache.activemq:activemq-broker (Maven): from 6.0.0 before 6.3.3; before 5.19.12. org.apache.activemq:activemq-broker (Maven): from 6.0.0 before 6.3.3; before 5.19.12.Source: cve.now feed data

How do I fix CVE-2026-108949?

Upgrade to a fixed version: 6.3.3, 5.19.12.Source: cve.now feed data