NVD / CVE Program· CNA apache

CVE-2022-41678: Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE

Noroxi assessment

Priority: This week (action score 61/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 85.6% (FIRST EPSS); higher than 99.7% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Apache Software Foundation Apache ActiveMQ 5.16.6, 5.17.4.

Don’t wait for the next maintenance window. Upgrade to Apache Software Foundation Apache ActiveMQ 5.16.6, 5.17.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.8 · v3.1—Proof of concept Fix available

Published: Nov 28, 2023
Updated: Jun 17, 2026
EPSS: 85.6% · 99th percentile
CWE: CWE-287

Report tools

JSON

Action score

This week

Don’t wait for the next maintenance window.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 26 / 30 · 85.6%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	activemq	cpe:2.3:a:apache:activemq

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache activemqbefore 5.16.6
apache activemq5.17.0 and later · before 5.17.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache ActiveMQ
- 5.18.0, 6.0.0not affected
- before 5.16.6affected · semver
- 5.17.0 and later · before 5.17.4affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:11	activemq	before 5.16.1-1+deb11u1	5.16.1-1+deb11u1
Debian:12	activemq	before 5.17.2+dfsg-2+deb12u1	5.17.2+dfsg-2+deb12u1
Debian:13	activemq	before 5.17.6+dfsg-1	5.17.6+dfsg-1
Maven	org.apache.activemq:apache-activemq	from 5.17.0 · before 5.17.4	5.17.4
Maven	org.apache.activemq:apache-activemq	before 5.16.6	5.16.6

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2023-46604Apache ActiveMQ, Apache ActiveMQ Legacy OpenWire Module: Unbounded deserialization causes ActiveMQ to be vulnerable to a remote code execution (RCE) attackKEV
99Now
CVE-2016-3088The Fileserver web application in Apache ActiveMQ 5.x before 5.14.0 allows remote attackers to upload and execute arbitrary files via an HTTKEV
99Now
CVE-2026-34197Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeansKEV
94Now

Published before and after this one in the same product

← EarlierCVE-2021-26117Jan 27, 2021 · ActiveMQ: LDAP-Authentication does not verify passwords on servers with anonymous bind
33Monitor
← EarlierCVE-2020-13947Feb 8, 2021 · An instance of a cross-site scripting vulnerability was identified to be present in the web based administration console on the message.jsp
48Plan
Later →CVE-2024-32114May 2, 2024 · Apache ActiveMQ: Jolokia and REST API were not secured with default configuration
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache ActiveMQ	5.16.6	Vendor (CNA)
Apache Software Foundation Apache ActiveMQ	5.17.4	Vendor (CNA)
debian:activemq	5.17.2+dfsg-2+deb12u1 · Debian:12	Package registry (OSV)
Maven:org.apache.activemq:apache-activemq	5.16.6	Package registry (OSV)
Maven:org.apache.activemq:apache-activemq	5.17.4	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1
Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2022-41678	—
Proof-of-concept repository on GitHub	stars:2	2024-11-28
Proof-of-concept repository on GitHub	stars:2	2025-10-14
Proof-of-concept repository on GitHub	stars:86	2026-04-20

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedNov 28, 2023
First PoCNov 28, 2024+365 d
TodayNov 8, 2026+1076 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

activemq.apache.org/security-advisories.data/CVE-2022-41678-announcement.txt

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records