CVE-2026-57822
Apache Artemis, Apache ActiveMQ Artemis: Message-based management parameter deserialization may lead to denial of service
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
Apache Artemis, Apache ActiveMQ Artemis: Message-based management parameter deserialization may lead to denial of service
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.
- Record
CVE-2026-57822- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-502
- Updated
- 2026-11-02
EUVDEUVD-2026-75247
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.
- Record
EUVD-2026-75247- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-73q3-xq4g-44wj
When the broker is processing message-based management requests, sent by an authenticated...
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.
- Record
GHSA-73q3-xq4g-44wj- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-502
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2026-57822- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-502
- Updated
- 2026-11-02
OSV
Apache Artemis, Apache ActiveMQ Artemis: Message-based management parameter deserialization may lead to denial of service
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.
- Record
CVE-2026-57822- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVCLSA-2026-1791377217 No score
TuxCare security update for org.apache.activemq (3 CVEs)
TuxCare rebuilt 4 org.apache.activemq packages to address 3 CVEs. Fixed in 2.33.0-tuxcare.7.
- Record
CLSA-2026-1791377217- Updated
- 2026-11-02
OSVCLSA-2026-1793195078 No score
TuxCare security update for org.apache.activemq (5 CVEs)
TuxCare rebuilt 5 org.apache.activemq packages to address 5 CVEs. Fixed in 2.37.0-tuxcare.3.
- Record
CLSA-2026-1793195078- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.apache.activemq:artemis-core-clientTuxCare:Maven From an advisory covering 3 CVEs |
2.33.0 up to 2.33.0-tuxcare.7, plus listed versions 2.33.0-tuxcare.12.33.0-tuxcare.22.33.0-tuxcare.32.33.0-tuxcare.42.33.0-tuxcare.52.33.0-tuxcare.6 |
2.33.0-tuxcare.7 |
org.apache.activemq:artemis-jakarta-openwire-protocolTuxCare:Maven From an advisory covering 3 CVEs |
2.33.0 up to 2.33.0-tuxcare.7, plus listed versions 2.33.0-tuxcare.12.33.0-tuxcare.22.33.0-tuxcare.32.33.0-tuxcare.42.33.0-tuxcare.52.33.0-tuxcare.6 |
2.33.0-tuxcare.7 |
org.apache.activemq:artemis-openwire-protocolTuxCare:Maven From an advisory covering 3 CVEs |
2.33.0 up to 2.33.0-tuxcare.7, plus listed versions 2.33.0-tuxcare.12.33.0-tuxcare.22.33.0-tuxcare.32.33.0-tuxcare.42.33.0-tuxcare.52.33.0-tuxcare.6 |
2.33.0-tuxcare.7 |
org.apache.activemq:artemis-serverTuxCare:Maven From an advisory covering 3 CVEs |
2.33.0 up to 2.33.0-tuxcare.7, plus listed versions 2.33.0-tuxcare.12.33.0-tuxcare.22.33.0-tuxcare.32.33.0-tuxcare.42.33.0-tuxcare.52.33.0-tuxcare.6 |
2.33.0-tuxcare.7 |
org.apache.activemq:artemis-core-clientTuxCare:Maven From an advisory covering 5 CVEs |
2.37.0 up to 2.37.0-tuxcare.3, plus listed versions 2.37.0-tuxcare.12.37.0-tuxcare.2 |
2.37.0-tuxcare.3 |
org.apache.activemq:artemis-jakarta-openwire-protocolTuxCare:Maven From an advisory covering 5 CVEs |
2.37.0 up to 2.37.0-tuxcare.3, plus listed versions 2.37.0-tuxcare.12.37.0-tuxcare.2 |
2.37.0-tuxcare.3 |
org.apache.activemq:artemis-openwire-protocolTuxCare:Maven From an advisory covering 5 CVEs |
2.37.0 up to 2.37.0-tuxcare.3, plus listed versions 2.37.0-tuxcare.12.37.0-tuxcare.2 |
2.37.0-tuxcare.3 |
org.apache.activemq:artemis-selectorTuxCare:Maven From an advisory covering 5 CVEs |
2.37.0 up to 2.37.0-tuxcare.3, plus listed versions 2.37.0-tuxcare.12.37.0-tuxcare.2 |
2.37.0-tuxcare.3 |
org.apache.activemq:artemis-serverTuxCare:Maven From an advisory covering 5 CVEs |
2.37.0 up to 2.37.0-tuxcare.3, plus listed versions 2.37.0-tuxcare.12.37.0-tuxcare.2 |
2.37.0-tuxcare.3 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-57822 is a medium vulnerability (CVSS 6.5) in Apache Artemis, published September 10, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.70%, the 53rd percentile. No source names a fixed version.