CVE-2022-41678

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 86% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 86%
CISA-KEV: Not listedEPSS PROB: 86%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. 

In details, in ActiveMQ configurations, jetty allows org.jolokia.http.AgentServlet to handler request to /api/jolokia

org.jolokia.http.HttpRequestHandler#handlePostRequest is able to create JmxRequest through JSONObject. And calls to org.jolokia.http.HttpRequestHandler#executeRequest.

Into deeper calling stacks, org.jolokia.handler.ExecHandler#doHandleRequest can be invoked through refection. This could lead to RCE through via various mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.

1 Call newRecording.

2 Call setConfiguration. And a webshell data hides in it.

3 Call startRecording.

4 Call copyTo method. The webshell will be written to a .jsp file.

The mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia. A more restrictive Jolokia configuration has been defined in default ActiveMQ distribution. We encourage users to upgrade to ActiveMQ distributions version including updated Jolokia configuration: 5.16.6, 5.17.4, 5.18.0, 6.0.0.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
79
EG Risk 79/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation86% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
86%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 28, 2023

Last Modified

November 3, 2025

Advisory Details (5)

Auto-updated Aug 2, 2026
Patch available.
generic

oss-security - CVE-2022-41678: Apache ActiveMQ: Deserialization vulnerability on Jolokia that allows authenticated users to perform RCE

https://www.openwall.com/lists/oss-security/2023/11/28/1
genericMentions a patch (unverified)

[SECURITY] [DLA 3936-1] activemq security update

https://lists.debian.org/debian-lts-announce/2024/10/msg00027.html

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibactivemq-java-doc (5.13.2+dfsg-2ubuntu0.1~esm1) @ xenial2026-05-24ubuntu
ubuntulibactivemq-java (5.16.1-1ubuntu0.1) @ jammy2026-05-24ubuntu
redhatactivemq2024-05-23redhat
redhatamq7/amq-broker-rhel8-operator-bundle:7.12.0-102024-05-21redhat
redhatpatch2024-05-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
activemq5.16.1-1
  • every version up to 5.16.1-1+deb11u1: fixed in 5.16.1-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
activemq5.17.2+dfsg-2
  • every version up to 5.17.2+dfsg-2+deb12u1: fixed in 5.17.2+dfsg-2+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
activemq—
  • every version up to 5.17.6+dfsg-1: fixed in 5.17.6+dfsg-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.activemq:apache-activemq5.17.0, 5.17.1, 5.17.2, 5.17.3
  • every version up to 5.16.6: fixed in 5.16.6
  • 5.17.0 up to 5.17.4: fixed in 5.17.4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 2× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-06 15:14 UTCEPSS rescore
  3. 2026-10-01 19:47 UTCEPSS rescore
  4. 2026-09-30 16:06 UTCEG score recompute
  5. 2026-09-26 15:55 UTCEPSS rescore
  6. 2026-09-26 00:22 UTCEPSS rescore
  7. 2026-09-22 15:22 UTCOSV refresh
  8. 2026-09-19 15:38 UTCEPSS rescore
  9. 2026-09-16 14:05 UTCEPSS rescore
  10. 2026-09-06 13:45 UTCEPSS rescore
  11. 2026-09-05 15:25 UTCEPSS rescore
  12. 2026-09-04 13:57 UTCEPSS rescore
  13. 2026-09-04 05:04 UTCEPSS rescore
  14. 2026-09-03 12:29 UTCOSV refresh
  15. 2026-08-30 19:15 UTCEPSS rescore
  16. 2026-08-30 19:14 UTCEPSS rescore
  17. 2026-08-28 21:38 UTCEPSS rescore
  18. 2026-08-26 14:43 UTCEPSS rescore
  19. 2026-08-25 13:46 UTCEPSS rescore
  20. 2026-08-24 14:13 UTCEPSS rescore
  21. 2026-08-21 23:46 UTCEPSS rescore
  22. 2026-08-19 17:01 UTCEPSS rescore
  23. 2026-08-19 17:01 UTCEPSS rescore
  24. 2026-08-17 01:48 UTCOSV refresh
  25. 2026-08-16 02:12 UTCEPSS rescore
Show 53 more
  1. 2026-08-12 13:48 UTCEPSS rescore
  2. 2026-08-11 13:39 UTCEPSS rescore
  3. 2026-08-08 16:34 UTCEPSS rescore
  4. 2026-08-07 16:24 UTCEPSS rescore
  5. 2026-08-04 10:35 UTCEPSS rescore
  6. 2026-08-01 20:06 UTCOSV refresh
  7. 2026-07-30 01:28 UTCEPSS rescore
  8. 2026-07-28 15:34 UTCEPSS rescore
  9. 2026-07-24 14:15 UTCEPSS rescore
  10. 2026-07-23 02:14 UTCEG score recompute
  11. 2026-07-22 23:01 UTCEG score recompute
  12. 2026-07-22 14:06 UTCEPSS rescore
  13. 2026-07-20 17:05 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 03:19 UTCOSV refresh
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-11 08:25 UTCEPSS rescore
  19. 2026-07-11 08:25 UTCEPSS rescore
  20. 2026-07-05 02:28 UTCEPSS rescore
  21. 2026-07-01 15:04 UTCEPSS rescore
  22. 2026-06-27 03:37 UTCOSV refresh
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-25 13:48 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
  26. 2026-06-23 21:31 UTCEPSS rescore
  27. 2026-06-18 17:51 UTCEPSS rescore
  28. 2026-06-18 17:51 UTCEPSS rescore
  29. 2026-06-17 17:51 UTCEPSS rescore
  30. 2026-06-17 17:51 UTCEPSS rescore
  31. 2026-06-15 17:46 UTCEPSS rescore
  32. 2026-06-14 23:16 UTCEPSS rescore
  33. 2026-06-11 13:58 UTCEPSS rescore
  34. 2026-06-11 13:58 UTCEPSS rescore
  35. 2026-06-10 13:21 UTCEPSS rescore
  36. 2026-06-10 13:21 UTCEPSS rescore
  37. 2026-06-09 14:17 UTCOSV refresh
  38. 2026-06-08 14:15 UTCEPSS rescore
  39. 2026-06-07 15:23 UTCEPSS rescore
  40. 2026-06-07 15:23 UTCEPSS rescore
  41. 2026-06-05 22:46 UTCEPSS rescore
  42. 2026-06-05 22:46 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-06-01 13:50 UTCEPSS rescore
  45. 2026-05-29 13:43 UTCEPSS rescore
  46. 2026-05-26 13:43 UTCEPSS rescore
  47. 2026-05-26 13:43 UTCEPSS rescore
  48. 2026-05-26 13:43 UTCEPSS rescore
  49. 2026-05-26 07:17 UTCEPSS rescore
  50. 2026-05-26 07:17 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-24 13:14 UTCEG score recompute
  53. 2026-05-24 13:14 UTCVendor advisory

Publicly available exploits

(4 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCCatherines77/ActiveMQ-EXPtools
    First seen Apr 20, 2026

    Apache ActiveMQ漏洞综合利用工具(CVE-2015-5254,CVE-2016-3088,CVE-2022-41678,CVE-2023-46604,CVE-2024-32114,CVE-2026-34197,CVE-2026-40466)

    Open source ↗
  • GitHub PoCURJACK2025/CVE-2022-41678
    First seen Oct 14, 2025

    CVE-2022-41678 是 Apache ActiveMQ 中的一个远程代码执行漏洞。该漏洞允许攻击者通过 JMX (Java Management Extensions) 接口修改 Log4j 配置或 JFR (Java Flight Recorder) 配置,从而写入恶意的 JSP webshell 到服务器的 web 目录中,最终实现远程代码执行。

    Open source ↗
  • GitHub PoCmbadanoiu/CVE-2022-41678
    First seen Nov 28, 2024

    CVE-2022-41678: Dangerous MBeans Accessible via Jolokia API in Apache ActiveMQ

    Open source ↗
  • Nucleihttp/cves/2022/CVE-2022-41678.yaml
    First seen Jan 1, 2022

    Apache ActiveMQ < 5.16.5/5.17.3 - Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2022-41678?
CVE-2022-41678 is a critical vulnerability published on November 28, 2023. Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. In details, in ActiveMQ configurations, jetty allows org.jolokia.http.AgentServlet to handler request to /api/jolokia org.jolokia.http.HttpRequestHandler#handlePostRequest is able to create JmxRequest…
When was CVE-2022-41678 disclosed?
CVE-2022-41678 was first published on November 28, 2023, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-41678 actively exploited?
CVE-2022-41678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 86% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-41678?
CVE-2022-41678 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2022-41678?
A fix for CVE-2022-41678 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-41678 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-41678

Explore →

Is Your Infrastructure Affected by CVE-2022-41678?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.