# What is CVE-2022-41678? > CVE-2022-41678 is a high-severity flaw (CVSS 8.8) in Activemq from Apache, published on 28 November 2023. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 86%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-41678 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 73 out of 100 (High); action: Patch now. Kept up to date as the evidence changes. - **Severity:** High (CVSS 8.8 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 86% (latest exploit-likelihood forecast) - **Published:** 28 November 2023 - **Record last updated:** 3 November 2025 - **Main product:** Activemq from Apache - **Affected products:** 1 ## What is CVE-2022-41678? In plain terms It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### The official 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. ### What kind of flaw is it? - CWE-287: Improper Authentication ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read data, change data and take it offline Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` ## Is CVE-2022-41678 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 86%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 86%, 86%, 86%, 86%, 86%, 86%, 86%. ### Timeline - 28 November 2023: Published - 11 June 2025: Exploit likelihood jumped - 3 November 2025: Record last updated - 22 November 2025: Exploit likelihood fell ### How Precursor Intelligence ranks it CVE-2022-41678 scores **73 out of 100 (High)**, with the action "Patch now". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2022-41678? The published record lists 1 product. Versions are as published: "before 5.16.6" means every version up to, but not including, 5.16.6. - [Activemq](https://www.precursorintelligence.com/product/apache/activemq) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): before 5.16.6, 5.17.0 to before 5.17.4 ## How do I fix CVE-2022-41678? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [activemq.apache.org](https://activemq.apache.org/security-advisories.data/CVE-2022-41678-announcement.txt) (Vendor advisory) - [lists.apache.org](https://lists.apache.org/thread/7g17kwbtjl011mm4tr8bn1vnoq9wh4sl) (Mailing list, Vendor advisory) - [security.netapp.com](https://security.netapp.com/advisory/ntap-20240216-0004/) - [openwall.com](https://www.openwall.com/lists/oss-security/2023/11/28/1) - [lists.debian.org](https://lists.debian.org/debian-lts-announce/2024/10/msg00027.html) ## Questions ### What is CVE-2022-41678? CVE-2022-41678 is a high-severity flaw in Activemq from Apache, published on 28 November 2023. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### How serious is CVE-2022-41678? It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-41678 is 73 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2022-41678 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 86%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-41678 affect? For Activemq from Apache: before 5.16.6, 5.17.0 to before 5.17.4. ### How do I fix CVE-2022-41678? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2022-41678 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact