Skip to main content
← Vulnerabilities

Apache ActiveMQ, Apache ActiveMQ Runtime Config: ActiveMQ retains write access after live ACL revocation

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 6.3.3, 5.19.12
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 6.3.3, 5.19.12.

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

CVE-2026-111822 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache ActiveMQ and Apache ActiveMQ Runtime Config; fixed in 6.3.3 and 5.19.12.

Published
Last modified
Published
Not listed in CISA KEV
10/100 · provisional
Fix
Fixed in 6.3.3, 5.19.12
None on Exploit-DB, Metasploit or GitHub

Summary

Apache ActiveMQ and its Runtime Config plugin are affected: after a principal's write permission on a destination is removed at runtime, an already-authenticated connection opened before the change can keep sending to that destination, including through a new anonymous producer. Fresh connections and new explicit producers are correctly denied, and the advisory notes that the setup involves the runtime configuration plugin.

Read the original description

Improper invalidation of cached authorizations vulnerability in Apache ActiveMQ, Apache ActiveMQ Runtime Config. After the runtime configuration plugin removes a principal's write grant on a destination, an authenticated connection opened before the change can keep sending to that destination, including through a new anonymous producer, while fresh connections and new explicit producers are denied. This issue affects Apache ActiveMQ: from 6.0.0 before 6.3.3, before 5.19.12; Apache ActiveMQ Runtime Config: from 6.0.0 before 6.3.3, before 5.19.12. Users are recommended to upgrade to version 6.4.0, 6.3.3 or 5.19.12, which fixes the issue.

Impact

  • Widely used

    4 packages depend on org.apache.activemq:apache-activemq.Source: deps.dev

What to do

  • Upgrade to a fixed version: 6.3.3, 5.19.12.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • org.apache.activemq:apache-activemqMaven

    From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12

  • org.apache.activemq:activemq-runtime-configMaven

    From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12

Evidence 2

  1. Advisory
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-111822

Is CVE-2026-111822 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-111822?

org.apache.activemq:apache-activemq (Maven): from 6.0.0 before 6.3.3; before 5.19.12. org.apache.activemq:activemq-runtime-config (Maven): from 6.0.0 before 6.3.3; before 5.19.12.Source: cve.now feed data

How do I fix CVE-2026-111822?

Upgrade to a fixed version: 6.3.3, 5.19.12.Source: cve.now feed data