Skip to content
Fencer Vulns
medium 6.5

CVE-2026-57822 json

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

published 2026-09-10 1 mo ago modified 2026-09-16 54 d ago also EUVD-2026-75247

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • apache artemis 2.44.0, 2.57.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-57822 updated cvss 4.9

artemis-core-client: activemq-artemis: Unsafe deserialization via JsonUtil CompositeData on management address

  • Red Hat build of Apache Camel 4 for Quarkus 3 artemis-core-client 2.53.0.redhat-00003
    affected: workaround, no fix available
  • Red Hat Fuse 7 artemis-core-client 2.53.0.redhat-00003
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat JBoss Enterprise Application Platform 7 artemis-core-client 2.53.0.redhat-00003
    affected: workaround, no fix planned “Will not fix”
  • Red Hat JBoss Enterprise Application Platform 8 artemis-core-client 2.53.0.redhat-00003
    affected: workaround, no fix available
  • Red Hat Satellite 6 candlepin, candlepin-selinux
    affected: workaround, no fix available “Fix deferred”
  • Red Hat AMQ Broker 7.13.6
    fixed: vendor fix RHSA-2026:66545
  • Red Hat AMQ Broker 7.14.1
    fixed: vendor fix RHSA-2026:66488
  • Red Hat build of Apache Camel for Spring Boot 4 artemis-core-client 2.53.0.redhat-00003
    not affected: vulnerable code not present
show 2 more
  • Red Hat JBoss Enterprise Application Platform Expansion Pack artemis-core-client 2.53.0.redhat-00003
    not affected: component not present
  • Red Hat Single Sign-On 7 artemis-core-client 2.53.0.redhat-00003
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
1 mo ago

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Apache Software Foundation Apache Artemis
  • Apache Software Foundation Apache ActiveMQ Artemis

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.