Medium [CVE-2026-57822] Unsafe deserialization via JsonUtil CompositeData on management address
This medium-severity Red Hat Linux advisory covers CVE-2026-57822 affecting Red Hat AMQ Broker 7, Red Hat Fuse 7, Red Hat JBoss Enterprise Application Platform 7.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Apache ActiveMQ Artemis. The JsonUtil.fromJsonArray() method uses ObjectInputStream.readObject() to deserialize CompositeData from Base64-encoded serialized objects in management message bodies sent to the activemq.management address.
While the deserialization is protected by an allowlist (java.util,java.lang,javax.management) that blocks RCE gadget chains, an authenticated attacker with the MANAGE role can craft a deserialization bomb using deeply nested java.util.
HashSet/HashMap structures to exhaust CPU/memory and crash the broker JVM, causing denial of service for all connected clients. Red Hat severity: Moderate — CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-502. Affected Red Hat products: Red Hat AMQ Broker 7; Red Hat Fuse 7; Red Hat JBoss Enterprise Application Platform 7; Red Hat JBoss Enterprise Application Platform 8; Red Hat JBoss Enterprise Application Platform Expansion Pack.
Red Hat lists Red Hat build of Apache Camel for Spring Boot 4; Red Hat Single Sign-On 7 as not affected. Will not fix / out of support: Red Hat Fuse 7; Red Hat JBoss Enterprise Application Platform 7.
Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Restrict MANAGE role access: ensure only trusted administrative accounts have the manage permission on the activemq.management address. Review security-setting configurations in standalone-full.xml (EAP) or broker.xml (AMQ Broker) to confirm management address role assignments follow least-privilege principles. Additionally, restrict network access to messaging ports (default 61616) so that management operations are only accessible from administrative networks.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.