Quick answers
- Is CVE-2026-61487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61487 being exploited in the wild.
- How severe is CVE-2026-61487?
- Informational severity, with a CVSS score of 0, published 28 July 2026.
- Which products and versions are affected?
- Apache ActiveMQ < 5.19.9, 6.0.0 to < 6.2.8.
- Is there a fix for CVE-2026-61487?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-61487 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61487?
- 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.
Technical details
An improper authorization vulnerability exists in Apache ActiveMQ's handling of temporary composite destinations. An authenticated attacker with low privileges can bypass per-destination write ACLs by sending messages to a temporary composite destination whose physical name contains a comma-separated list of legitimate, restricted queues. Because the broker marks the destination as 'temporary', it incorrectly skips standard authorization checks, allowing the attacker to publish messages to any queue in the composite list. This affects ActiveMQ Broker, ActiveMQ All, and the main ActiveMQ distribution across versions 5.x and 6.x. Users should upgrade to 5.19.9, 6.2.8, or 6.3.0 to resolve the issue.
Affected products
- Apache ActiveMQ Broker < 5.19.9, 6.0.0 to < 6.2.8
- Apache ActiveMQ All < 5.19.9, 6.0.0 to < 6.2.8
- Apache ActiveMQ < 5.19.9, 6.0.0 to < 6.2.8
Timeline
- 2026-07-27: disclosed: Initial disclosure on oss-security mailing list
- 2026-07-28: advisory: NVD publication date