How severe is CVE-2022-23913?

CVE-2022-23913 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-23913?

CVE-2022-23913 affects the following packages: org.apache.activemq:artemis-core-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-23913?

Update org.apache.activemq:artemis-core-client to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23913 is resolved across your whole dependency graph.

How do I detect CVE-2022-23913 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:artemis-core-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-23913 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-23913 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-23913, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-23913?

CVE-2022-23913 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-23913?

CVE-2022-23913 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-23913 published, and has it been updated?

CVE-2022-23913 was published on February 4, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-23913 — artemis-core-client

HIGHFix: apache/activemq-artemis#3862

CVE-2022-23913 is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.apache.activemq:artemis-core-client. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.activemq:artemis-core-client — see the affected versions and patch details below.

Apache ActiveMQ Artemis DoS

Also known asGHSA-pr38-qpxm-g88x

Published

Feb 4, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.activemq:artemis-core-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:artemis-core-client`	all versions	2.19.1`org.apache.activemq:artemis-core-client:2.19.1`

Affected Products

3 products · 3 configurations

Application

artemisapache

< 2.19.1

range

Application

active iq unified managernetapp

all

Application

oncommand workflow automationnetapp

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could …

lists.apache.orgNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:artemis-core-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:artemis-core-client to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23913 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat AMQ 7.10.0	`artemis-commons`	RHSA-2022:5101
Red Hat Fuse 7.11	`artemis-commons`	RHSA-2022:5532
Red Hat JBoss Enterprise Application Platform	`org.apache.activemq/artemis-commons:2.16.0.redhat-00042`	RHSA-2022:4922
Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7	`eap7-activemq-artemis-0:1.5.5.016-1.redhat_00001.1.ep7.el7`	RHSA-2025:4226
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7	`eap7-activemq-artemis-0:2.9.0-10.redhat_00021.1.el7eap`	RHSA-2025:4437
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-activemq-artemis-0:2.16.0-9.redhat_00042.1.el8eap`	RHSA-2022:4919
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-activemq-artemis-0:2.16.0-9.redhat_00042.1.el7eap`	RHSA-2022:4918
Red Hat Single Sign-On 7.6.1	see advisory	RHSA-2022:7417

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2022-23913 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-770CWE-770

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Feb 4, 2022

First exploit

Feb 10, 2022

6 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-23913

GHSA-pr38-qpxm-g88x

References

Advisorygithub.com · CVE 2022 23913.json Advisorynvd.nist.gov · CVE 2022 23913 Advisorysecurity.netapp.com · ntap 20220303 0003 Weblists.apache.org · fjynj57rd99s814rdn5hzvmx8lz403q2 Webgithub.com Webgithub.com Webgithub.com · 1f92368240229b8f5db92a92a72c703faf83e9b7 Webgithub.com Webgithub.com · 153d2e9a979aead8dff95fbc91d659ecc7d0fb82 Webissues.apache.org · ARTEMIS 3593 Websecurity.netapp.com · ntap 20220303 0003 Packagegithub.com · activemq artemis

Related vulnerabilities

Also affects artemis-core-client

This CVE is high severity — higher than any of the other 1 CVE affecting artemis-core-client (highest there: moderate).

CVE-2021-4040

Same weakness: CWE-770

This CVE is high severity; 3 of 7 other CVEs with CWE-770 are rated as high or higher (top: high).

CVE-2026-63501CVE-2026-59171CVE-2026-116773CVE-2026-119208CVE-2026-116775CVE-2026-116696CVE-2026-119209Browse all CWE-770

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-23913 — artemis-core-client

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-23913 in your dependencies?