Public proof of conceptFix available

CVE-2022-41678

Q: Is CVE-2022-41678 actively exploited?

Active exploitation of CVE-2022-41678 has not been confirmed. Its EPSS score was 85.8% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2022-41678?

CVE-2022-41678 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

A public proof of concept exists; no exploitation attested.

Published2023-11-28
Fixed in5.17.4 · 5.16.6
WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC

2023-11-2816:15CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-41678?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-41678?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV

Apache activemq

Branch	Affected	Fixed in	Source
5.17	≥ 5.17.0, < 5.17.4	5.17.4	NVD · OSV
5.16	< 5.16.6	5.16.6	NVD · OSV

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

RHSA-2024:2944 Red Hat Product Security9 products fixed
Red Hat Security Advisory: AMQ Broker 7.12.0.OPR.1.GA Container Images release and security update

Full record on NVD

Fix

Update Apache activemq to 5.17.4 · 5.16.6
Vendor fix Red Hat Product Security RHSA-2024:2944 · 9 productsTo update to the latest image please refer to the AMQ container images in the Red Hat Container catalog.
Workaround from the vendor Red Hat Product Security RHSA-2024:2944 · 13 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Advisories and patches

activemq.apache.orgVendor Advisory
lists.apache.orgVendor Advisory

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 3 repositories, unverifiedmbadanoiu/CVE-2022-41678URJACK2025/CVE-2022-41678Catherines77/ActiveMQ-EXPtools

Sources

NVDCVSS 3.18.8read 2026-10-23
CNAweakness (CWE)CWE-287read 2026-10-23
FIRST EPSSEPSS score85.8 %read 2026-10-23
PoC-in-GitHubproof of concept3read 2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published: 2023-11-28
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2022-41678?

Is CVE-2022-41678 actively exploited?

Active exploitation of CVE-2022-41678 has not been confirmed. Its EPSS score was 85.8% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-41678?

CVE-2022-41678 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running activemq? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database