Quick answers
- Is CVE-2026-108500 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108500 being exploited in the wild.
- How severe is CVE-2026-108500?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Apache ActiveMQ 5.19.0 to 5.19.11, 6.3.0 to 6.3.2.
- Is there a fix for CVE-2026-108500?
- Yes: fixed in ActiveMQ 5.19.12, 6.3.3, 6.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108500 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108500?
- Check whether you run Apache ActiveMQ 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 5.19.12, 6.3.3, 6.4.0
Technical details
An input validation vulnerability in the LDAPAuthorizationMapPlugin fails to sanitize destination names containing LDAP DN special characters (comma, plus, equals, backslash), allowing an authenticated attacker to inject LDAP search expressions. This manipulation of the LDAP search base used for ACL lookups enables privilege escalation or ACL bypass. The vulnerability requires prior authentication and LDAP-based authorization configuration.
Affected products
- Apache ActiveMQ 5.19.0 to 5.19.11, 6.3.0 to 6.3.2
Timeline
- 2026-11-04: disclosed