REDHAT-BUG-2457275: High severity Apache ActiveMQ Client vulnerability

Published Apr 10, 2026
·
Updated

Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ.

ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS.

Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4.

Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.

Affected Software

3 affected components
Apache ActiveMQ Client>6.0.0<=6.2.4, <5.19.4
Apache ActiveMQ Broker>6.0.0<=6.2.4, <5.19.4
Apache ActiveMQ>6.0.0<=6.2.4, <5.19.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.19.5
  2. Upgrade

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

    Fixed in 5.19.5
  3. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 5.19.5
  4. Upgrade

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

    Fixed in 6.2.4
  5. Upgrade

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

    Fixed in 6.2.4
  6. Upgrade

    Upgrade Apache ActiveMQ to a version that resolves this vulnerability.

    Fixed in 6.2.4

Event History

Apr 10, 2026
Data Sourced
via Red Hat·11:01 AM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2457275?

The severity of REDHAT-BUG-2457275 is high with a score of 7.

2

What software is affected by REDHAT-BUG-2457275?

The affected software includes Apache ActiveMQ Client, Apache ActiveMQ Broker, and Apache ActiveMQ.

3

How do I fix REDHAT-BUG-2457275?

Fixing REDHAT-BUG-2457275 involves updating to the latest version of Apache ActiveMQ that addresses the Out of Memory vulnerability.

4

What type of vulnerability is REDHAT-BUG-2457275 associated with?

REDHAT-BUG-2457275 is associated with a Denial of Service vulnerability.

5

What causes the vulnerability in REDHAT-BUG-2457275?

The vulnerability in REDHAT-BUG-2457275 is caused by improper handling of TLSv1.3 handshake KeyUpdates in ActiveMQ NIO SSL transports.

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