High Artemis CVEs
11 CVEs, 2 protected by Waratek
Overview 11 matches · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
2
18.2%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
9
81.8%
blocked by ARMR today
2
18.2%
partly blocked
0
0.0%
not blocked
9
81.8%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
2
18.2%
Forecast only
0
0.0%
No public exploit
9
81.8%
split by
peak 4 / year
20161
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
20170
20181
No exploit published1
High1
not blocked1
No public exploit1
20190
20200
20212
No exploit published2
High2
not blocked2
No public exploit2
20221
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
20230
20244
No exploit published4
High4
not blocked4
Proof of concept only2
No public exploit2
20250
20262
No exploit published2
High2
not blocked2
No public exploit2
20162017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-49363 | High | 2026-09-10 | No exploit published | No public exploit | An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue. |
| CVE-2026-49362 | High | 2026-09-10 | No exploit published | No public exploit | An unauthenticated remote attacker can create arbitrary durable queues via the CORE protocol, leading to unauthorized broker state manipulation and potential denial of service. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue. |
| CVE-2023-50780 | High | 2024-10-14 | No exploit published | No public exploit | Apache ActiveMQ Artemis allows access to diagnostic information and controls through MBeans, which are also exposed through the authenticated Jolokia endpoint. Before version 2.29.0, this also included the Log4J2 MBean. This MBean is not meant for exposure to non-administrative users. This could eventually allow an authenticated attacker to write arbitrary files to the filesystem and indirectly achieve RCE. Users are recommended to upgrade to version 2.29.0 or later, which fixes the issue. |
| CVE-2024-23683 | High | 2024-01-19 | No exploit published | Proof of concept only | Artemis Java Test Sandbox versions less than 1.7.6 are vulnerable to a sandbox escape when an attacker crafts a special subclass of InvocationTargetException. An attacker can abuse this issue to execute arbitrary Java when a victim executes the supposedly sandboxed code. |
| CVE-2024-23682 | High | 2024-01-19 | No exploit published | No public exploit | Artemis Java Test Sandbox versions before 1.8.0 are vulnerable to a sandbox escape when an attacker includes class files in a package that Ares trusts. An attacker can abuse this issue to execute arbitrary Java when a victim executes the supposedly sandboxed code. |
| CVE-2024-23681 | High | 2024-01-19 | No exploit published | Proof of concept only | Artemis Java Test Sandbox versions before 1.11.2 are vulnerable to a sandbox escape when an attacker loads untrusted libraries using System.load or System.loadLibrary. An attacker can abuse this issue to execute arbitrary Java when a victim executes the supposedly sandboxed code. |
| CVE-2022-23913 | High | 2022-02-04 | Protected by Waratek | No public exploit | In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory. |
| CVE-2021-26118 | High | 2021-01-27 | No exploit published | No public exploit | While investigating ARTEMIS-2964 it was found that the creation of advisory messages in the OpenWire protocol head of Apache ActiveMQ Artemis 2.15.0 bypassed policy based access control for the entire session. Production of advisory messages was not subject to access control in error. |
| CVE-2021-26117 | High | 2021-01-27 | No exploit published | No public exploit | The optional ActiveMQ LDAP login module can be configured to use anonymous access to the LDAP server. In this case, for Apache ActiveMQ Artemis prior to version 2.16.0 and Apache ActiveMQ prior to versions 5.16.1 and 5.15.14, the anonymous context is used to verify a valid users password in error, resulting in no check on the password. |
| CVE-2017-12174 | High | 2018-03-07 | No exploit published | No public exploit | It was found that when Artemis and HornetQ before 2.4.0 are configured with UDP discovery and JGroups discovery a huge byte array is created when receiving an unexpected multicast message. This may result in a heap memory exhaustion, full GC, or OutOfMemoryError. |
| CVE-2016-4978 | High | 2016-09-27 | Protected by Waratek | No public exploit | The getObject method of the javax.jms.ObjectMessage class in the (1) JMS Core client, (2) Artemis broker, and (3) Artemis REST component in Apache ActiveMQ Artemis before 1.4.0 might allow remote authenticated users with permission to send messages to the Artemis broker to deserialize arbitrary objects and execute arbitrary code by leveraging gadget classes being present on the Artemis classpath. |