CVE-2026-57822: Apache Artemis, Apache ActiveMQ Artemis: Message-based management parameter deserialization may lead to denial of service

Published Sep 10, 2026
·
Updated

When the broker is processing message-based management requests, sent by an authenticated messaging client that is authorized with MANAGE permission to perform management-via-messaging, the parameter processing can trigger Java deserialization of certain method parameters that the broker will not utilise. The permitted types allow to craft a payload causing excessive computation and pinning the processing thread, leading to denial of service.

This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.3.0 through 2.44.0.

Users are recommended to upgrade to version 2.57.0, which fixes the issue.

Affected Software

2 affected components
Apache ARTEMIS>=2.50.0<=2.56.0
Apache ActiveMQ Artemis>=1.3.0<=2.44.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Artemis / Apache ActiveMQ Artemis to a version that resolves this vulnerability.

    Fixed in 2.57.0

Event History

Sep 10, 2026
CVE Published
via MITRE·04:46 AM
Data Sourced
via MITRE·04:46 AM
Description

Frequently Asked Questions

1

Who can exploit this issue?

An attacker must be an authenticated messaging client with MANAGE permission and authorization to perform management-via-messaging. Clients without those privileges are not described as able to trigger the vulnerable parameter processing.

2

Are brokers affected by default?

The issue is triggered only while processing message-based management requests. The provided information does not establish whether a default Artemis or ActiveMQ Artemis configuration grants clients the required MANAGE and management-via-messaging permissions.

3

What is the impact of a successful exploit?

A crafted permitted parameter type can cause excessive computation and pin a broker processing thread. This can lead to denial of service.

4

What should be done if an immediate upgrade is not possible?

Restrict MANAGE permission and management-via-messaging authorization to only trusted, necessary authenticated clients. This reduces access to the request path required to trigger the issue.

5

Which versions require remediation?

Apache Artemis versions 2.50.0 through 2.56.0 and Apache ActiveMQ Artemis versions 1.3.0 through 2.44.0 are affected. Upgrade to version 2.57.0 as recommended.

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