CVE-2026-74761: Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Spoofing of RemoveSubscription clientId

Published Sep 8, 2026
·
Updated

Improper input validation in TopicRegion in Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All on all platforms.

An authenticated client can spoof clientId when removing a durable topic subscription.

This issue affects Apache ActiveMQ Broker: before 5.19.11, from 6.0.0 before 6.3.2; Apache ActiveMQ All: before 5.19.11, from 6.0.0 before 6.3.2; Apache ActiveMQ: before 5.19.11, from 6.0.0 before 6.3.2.

Users are recommended to upgrade to version 6.3.2 or 5.19.11 which fixes the issue.

Affected Software

3 affected components
Apache ActiveMQ Broker>=6.0.0<6.3.2, <5.19.11
Apache ActiveMQ All>=6.0.0<6.3.2, <5.19.11
Apache ActiveMQ>=6.0.0<6.3.2, <5.19.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache ActiveMQ Broker to a version that resolves this vulnerability.

    Fixed in 6.3.2
  2. Upgrade

    Upgrade Apache ActiveMQ All to a version that resolves this vulnerability.

    Fixed in 6.3.2
  3. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 6.3.2
  4. Upgrade

    Upgrade Apache ActiveMQ Broker to a version that resolves this vulnerability.

    Fixed in 5.19.11
  5. Upgrade

    Upgrade Apache ActiveMQ All to a version that resolves this vulnerability.

    Fixed in 5.19.11
  6. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 5.19.11

Event History

Sep 9, 2026
CVE Published
via MITRE·11:10 AM
Data Sourced
via MITRE·11:10 AM
DescriptionWeakness

Frequently Asked Questions

1

What level of access does an attacker need?

The attacker must be an authenticated client. The issue is triggered when removing a durable topic subscription, where the client can spoof the clientId used for the removal.

2

Which deployments should be considered affected?

Affected releases are Apache ActiveMQ Broker, Apache ActiveMQ All, and Apache ActiveMQ before 5.19.11, and versions from 6.0.0 before 6.3.2. The issue applies on all platforms.

3

How can this be remediated?

Upgrade to Apache ActiveMQ version 5.19.11 or 6.3.2, which fix the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203