Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.70% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-57822High confidence
Apache Artemis, Apache ActiveMQ Artemis: Message-based management parameter deserialization may lead to denial of service
Apache Software Foundation · Apache Artemis
6.5MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Apache Software Foundation Apache Artemis and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-57822 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityartemis-core-client: activemq-artemis: Unsafe deserialization via JsonUtil CompositeData on management address
The vendor explicitly identifies these products as affected by this CVE.
- artemis-core-client as a component of Red Hat Fuse 7
- artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 7
- artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 8
- 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.
- Remediation
- Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
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.
What
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.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
What
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.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Deserialization of Untrusted Data → disrupt the affected service
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-502 ↗
CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Action
- Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 10 Sept 2026 · Last source change 10 Sept 2026, 15:53 UTC · CWE-502 · Deserialization of Untrusted Data
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-09-10
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-75247
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.3.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.3.0 ≤ 2.44.0 · Fixed: Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- artemis-core-client as a component of Red Hat Fuse 7; artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 7; artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 8; artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
- After
- artemis-core-client as a component of Red Hat Fuse 7; artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 7; artemis-core-client as a component of Red Hat JBoss Enterprise Application Platform 8 · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: lists.apache.org/0jmovbbvdo22zq1r91jrlhv02ck7jqzp.security@apache.org ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: lists.apache.org/0jmovbbvdo22zq1r91jrlhv02ck7jqzp
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 2.50.0 ≤ 2.56.0; 1.3.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.3.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- SeveritySeverity changed from Unknown to Medium.CISA ADP ↗
- Before
- Unknown
- After
- Medium
- CVSS scoreCVSS score changed from not recorded to 6.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).CISA ADP ↗
- Before
- not recorded
- After
- 6.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
- ENISA EUVD mappingEUVD-2026-75247 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-75247"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.