CVE-2026-101292

Artemis-core-client: unsafe reflection in apache activemq artemis federation message deserialization

HIGH
8.2
CVSS Score
Published: September 28, 2026 at 12:44 PM UTC
Updated: October 20, 2026 at 05:17 PM UTC
2 products affected across 1 vendorJBoss Enterprise Application PlatformAMQ Broker

Using Red Hat AMQ Broker 7 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat AMQ Broker 7 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Apache ActiveMQ Artemis before 2.34.0 contains an unsafe reflection vulnerability in FederationStreamConnectMessage.getFederationPolicy(). The method calls Class.forName(clazz).getConstructor().newInstance() where clazz is read directly from the CORE protocol wire buffer without type validation. An authenticated federation peer can send a FEDERATION_DOWNSTREAM_CONNECT packet with a crafted class name, causing the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. Static initializers (<clinit>) and no-argument constructors (<init>()) execute as side effects before the type cast, enabling denial of service via system-property poisoning, out-of-memory conditions via classloading, or broker state manipulation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
Vendor states this is fixed in 7 (unaffected)
All versions7
Vendor states this is fixed in 0:1.10.0-46.Final_redhat_00044.1.el7eap (unaffected)
Vendor states this is fixed in 0:1.5.26-2.Final_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.16.0-22.redhat_00057.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.18.8-1.redhat_00003.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.2.40-2.SP3_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.3.14-11.SP11_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.5.5-24.SP12_redhat_00016.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.5.5-30.SP12_redhat_00020.1.el7eap (unaffected)
Vendor states this is fixed in 0:4.1.135-1.Final_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:5.0.31-3.SP2_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:7.4.25-2.GA_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 2.16.0.redhat-57 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

Technical Descriptionx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:53644
VDB Entryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/security/cve/CVE-2026-101292
Issue Trackingx_refsource_REDHAT
Source: cverecord
https://bugzilla.redhat.com/show_bug.cgi?id=2482963
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:53806

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHredhat
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
HIGH
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-470

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card