ZeroHour
oss-securitypublished ()ingested
Part of a story covered by 7 sources: “Apache discloses seven vulnerabilities in Apache Artemis and ActiveMQ Artemis; five rated important, spanning unauthenticated queue creation/deletion, session hijack, credential…” — merged summary and timeline →

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

mediumVulnerabilityimportance 35CVE-2026-57822
AI summary · glm-5.3-flash

Apache fixed CVE-2026-57822, a deserialization flaw in ActiveMQ Artemis management messaging letting authorized clients trigger broker denial of service.

Apache disclosed a deserialization issue in message-based management request handling for Apache Artemis and Apache ActiveMQ Artemis. It affects Apache Artemis (artemis-core-client) 2.50.0 through 2.56.0 and ActiveMQ Artemis (artemis-core-client) 1.3.0 through 2.44.0. Exploitation requires an authenticated client authorized with MANAGE permission using management-via-messaging; parameter processing can trigger denial of service. Apache rates the issue as important.

  • Affects Artemis core-client 2.50.0-2.56.0 and ActiveMQ Artemis 1.3.0-2.44.0
  • Requires authenticated client with MANAGE permission via management messaging
  • Parameter deserialization in management requests can cause broker denial of service
  • Rated important by the Apache Security Team

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-57822
Authenticated deserialization DoS in Apache ActiveMQ Artemis brokers

When an Apache Artemis or Apache ActiveMQ Artemis broker processes message-based management requests, it deserializes certain method parameters—including ones the broker does not actually use—and the permitted types can be abused to craft a payload that forces excessive computation, pinning the processing thread and causing a denial of service. Triggering the flaw requires an authenticated messaging client that is authorized with the MANAGE permission to perform management-via-messaging, so anonymous or unprivileged clients cannot exploit it. An attacker with such access can repeatedly submit crafted management messages to tie up broker processing capacity, degrading or blocking message handling. Affected deployments run Apache ActiveMQ Artemis 1.3.0 through 2.44.0 or Apache Artemis 2.50.0 through 2.56.0; the fix ships in version 2.57.0. No public proof-of-concept or in-the-wild exploitation is known, and the issue has not yet been scored under CVSS.

Do: Upgrade to Apache Artemis 2.57.0, which fixes the issue. As an interim measure, audit which messaging users hold the MANAGE permission for management-via-messaging, restrict it to strictly trusted clients, and disable management-via-messaging on brokers that do not use the feature. Monitor broker processing threads for long-running, CPU-bound management-message handling as a sign of attempted abuse.

6.5<1%
  • Apache Artemis 2.50.0 through 2.56.0
  • Apache ActiveMQ Artemis 1.3.0 through 2.44.0
largeon the order of tens of thousands of broker deployments; only those with management-via-messaging enabled and a MANAGE-authorized messaging client are…
Full article

Posted by Clebert Suconic on Sep 09 Severity: important Affected versions: - Apache Artemis (org.apache.artemis:artemis-core-client) 2.50.0 through 2.56.0 - Apache ActiveMQ Artemis (org.apache.activemq:artemis-core-client) 1.3.0 through 2.44.0 Description: 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...

This source does not provide full text. Read it at seclists.org.