Skip to content
major vulnerability· requires attention

RCE in widely used Apache ActiveMQ Broker; could disrupt messaging infrastructure across industries.

Web

CVE-2026-34197

8.8
High
KEV · Exploited in wildEPSS 98%Patch availableApr 7, 2026

RCE via crafted Jolokia URI in Apache ActiveMQ Broker

common questions

Is CVE-2026-34197 being exploited?

Yes. CVE-2026-34197 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-34197?

CVE-2026-34197 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-34197?

Yes. A fix has been recorded for CVE-2026-34197. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-34197 affect?

CVE-2026-34197 affects Apache ActiveMQ Broker (versions <5.19.4 or 6.0.0<=v<6.2.3). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-34197?

Upgrade to 5.19.4/6.2.3; apply vendor mitigations

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache ActiveMQ Broker (versions <5.19.4 or 6.0.0<=v<6.2.3)
impact

Authenticated attacker can trigger remote code execution on the broker JVM via Spring XML context loading.

action required

Immediate action required

affected versions
Apache Software Foundation Apache ActiveMQ
  • affected< 5.19.4
  • affected>= 6.0.0 and < 6.2.3
Apache Software Foundation Apache ActiveMQ All
  • affected< 5.19.4
  • affected>= 6.0.0 and < 6.2.3
Apache Software Foundation Apache ActiveMQ Broker
  • affected< 5.19.4
  • affected>= 6.0.0 and < 6.2.3

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free