Widely deployed messaging middleware; RCE on broker could disrupt services across multiple industries.
CVE-2026-41044
RCE in ActiveMQ via crafted broker name in admin console.
Is CVE-2026-41044 being exploited?
Not confirmed. CVE-2026-41044 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.98% probability of exploitation in the next 30 days.
How severe is CVE-2026-41044?
CVE-2026-41044 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41044?
Yes. A fix has been recorded for CVE-2026-41044. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41044 affect?
CVE-2026-41044 affects Apache ActiveMQ 5.x before 5.19.6, Apache ActiveMQ 6.x before 6.2.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41044?
Upgrade to 6.2.5 or 5.19.6 now
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can trigger VM transport to load malicious Spring XML, causing RCE on broker JVM.
Immediate action required
- affected< 5.19.6
- affected>= 6.0.0 and < 6.2.5
- affected< 5.19.6
- affected>= 6.0.0 and < 6.2.5
- affected< 5.19.6
- affected>= 6.0.0 and < 6.2.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.