Quick answers
- Is CVE-2026-111822 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111822 being exploited in the wild.
- How severe is CVE-2026-111822?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Apache ActiveMQ 6.0.0 before 6.3.3, before 5.19.12; Apache ActiveMQ Runtime Config 6.0.0 before 6.3.3, before 5.19.12.
- Is there a fix for CVE-2026-111822?
- Yes: fixed in ActiveMQ 6.4.0, 6.3.3, 5.19.12. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111822 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111822?
- Check whether you run Apache ActiveMQ or Apache ActiveMQ Runtime Config at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ActiveMQ 6.4.0, 6.3.3, 5.19.12
Technical details
The runtime configuration plugin fails to invalidate cached authorization grants when a principal's write permission on a destination is removed. Authenticated connections established before the policy change retain their cached grants and can continue to send messages, while fresh connections and new explicit producers correctly enforce the updated policy. This affects both ActiveMQ and the Runtime Config component across multiple version branches.
Affected products
- Apache ActiveMQ 6.0.0 before 6.3.3, before 5.19.12
- Apache ActiveMQ Runtime Config 6.0.0 before 6.3.3, before 5.19.12
Timeline
- 2026-11-04: disclosed