CVE-2022-41678

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 93% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 86%
CISA-KEV: Not listedEPSS: 86%CVSS: 8.8Exploit: NoneExposed: 0

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.0(high)
EPSS
99.7%
KEV
Not listed

Published

November 28, 2023

Last Modified

November 3, 2025

References (9)

Vendor Advisories for CVE-2022-41678(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / 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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.activemq:apache-activemq5.17.0, 5.17.1, 5.17.2, 5.17.35.17.4—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 / 15× 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-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-05 02:28 UTCEPSS rescore
  4. 2026-07-01 15:04 UTCEPSS rescore
  5. 2026-06-27 03:37 UTCOSV refresh
  6. 2026-06-25 13:48 UTCEPSS rescore
  7. 2026-06-25 13:48 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-18 17:51 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-15 17:46 UTCEPSS rescore
  15. 2026-06-14 23:16 UTCEPSS rescore
  16. 2026-06-11 13:58 UTCEPSS rescore
  17. 2026-06-11 13:58 UTCEPSS rescore
  18. 2026-06-10 13:21 UTCEPSS rescore
  19. 2026-06-10 13:21 UTCEPSS rescore
  20. 2026-06-09 14:17 UTCOSV refresh
  21. 2026-06-08 14:15 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-07 15:23 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
Show 11 more
  1. 2026-06-01 13:50 UTCEPSS rescore
  2. 2026-06-01 13:50 UTCEPSS rescore
  3. 2026-05-29 13:43 UTCEPSS rescore
  4. 2026-05-26 13:43 UTCEPSS rescore
  5. 2026-05-26 13:43 UTCEPSS rescore
  6. 2026-05-26 13:43 UTCEPSS rescore
  7. 2026-05-26 07:17 UTCEPSS rescore
  8. 2026-05-26 07:17 UTCEPSS rescore
  9. 2026-05-26 07:17 UTCEPSS rescore
  10. 2026-05-24 13:14 UTCEG score recompute
  11. 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 high 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 in the National Vulnerability Database 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 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.
How do I remediate CVE-2022-41678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-41678, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs