`CVE-2026-57822` Apache Artemis

Affected software	Apache Artemis
Severity	6.5 Medium CVSS 3.1
Weakness	Deserialization of untrusted data (CWE-502)
Published	10 Sep 2026
Updated	16 Sep 2026

Published 2 months ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

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 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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC none indexed
EPSS 0.70% chance in 30 days

Waratek protection

Protected by Waratek

Waratek has a rule that blocks attacks on this vulnerability.

Protection full Deserialization
Action available security rule
Review automated Inferred
Record active

Decided by	A vulnerability class already blocked by an ARMR security rule
Finding	Protected by Waratek's ARMR deserialization DoS security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-502: Deserialization of Untrusted Data. Impact is availability-only (no confidentiality or integrity loss), so this is the DoS variant of the class, not RCE — the ARMR DoS rule applies rather than the RCE rule pair.

Decided by

A vulnerability class already blocked by an ARMR security rule

Finding

Protected by Waratek's ARMR deserialization DoS security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-502: Deserialization of Untrusted Data. Impact is availability-only (no confidentiality or integrity loss), so this is the DoS variant of the class, not RCE — the ARMR DoS rule applies rather than the RCE rule pair.

How to mitigate CVE-2026-57822

Apply the vendor's fix for Apache Artemis. Until you can, Waratek RASP blocks exploitation with its deserialization rule. It runs inside the Java application, with no code changes.

Waratek RASP Runtime protection for Java applications

Affected software and releases

Products and versions

1 product, 2 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	apache	artemis	generic	≥ 1.3.0 and ＜ 2.44.0 · ≥ 2.50.0 and ＜ 2.57.0

Source

Vendor

Product

Scheme

Affected versions

nvd

apache

artemis

generic

≥ 1.3.0 and ＜ 2.44.0 · ≥ 2.50.0 and ＜ 2.57.0

References

URL	Tags
https://lists.apache.org/thread/0jmovbbvdo22zq1r91jrlhv02ck7jqzp	Mailing List, Vendor Advisory
http://www.openwall.com/lists/oss-security/2026/09/10/4	Mailing List, Third Party Advisory

URL

Timeline

Published	2026-09-10	By the CVE Program.
NVD record modified	2026-09-16	NVD's own last-modified date for this record.

Published

2026-09-10

By the CVE Program.

NVD record modified

2026-09-16

NVD's own last-modified date for this record.

How VRT decided (18 of 24 rules ran)

18 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven no match An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package matched In scope CNA declares the affected component is a Maven artifact

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven no match The affected package being open source on Maven, so the fix can be read

19 poc-derivable no match An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit matched No exploit published No public exploits or POCs found in Exploit-DB, Nuclei templates, Metasploit modules, or GitHub POC repositories, and CISA's Vulnrichment assessment records no demonstrated exploit. No upstream fix reference or open-source Maven package was found either, so there is nothing to act on from either direction.

21 secure-rule-match decided it matched Protected by Waratek CWE-502 (Deserialization of Untrusted Data) is mitigable by an ARMR deserialization DoS security rule. Impact is availability-only (no confidentiality or integrity loss), so this is the DoS variant of the class, not RCE — the ARMR DoS rule applies rather than the RCE rule pair.

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold skipped Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published skipped Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

apache artemis not tracked cpe:2.3:a:apache:artemis:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗