CVE-2026-74761 Apache Software Foundation CVE debrief

Who should care

Defenders responsible for Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All deployments should assess exposure and apply patches to version 6.3.2 or 5.19.11. Defenders should prioritize verifying exposure and applying patches due to potential for authentication-based attacks. Affected versions require verification and patching to prevent potential authentication-based attacks.

Why it matters

CVE-2026-74761 is a high-severity vulnerability in Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All. Defenders should prioritize verifying exposure and applying patches due to potential for authentication-based attacks. The vulnerability allows an authenticated client to spoof clientId when removing a durable topic subscription. Affected versions require verification and patching to version 6.3.2 or 5.19.11.

• Potential for authentication-based attacks
• Spoofing of clientId when removing durable topic subscriptions
• Verification of exposure and patch application required

Technical summary

The vulnerability is due to improper input validation in TopicRegion, allowing an authenticated client to spoof clientId when removing a durable topic subscription. This issue affects Apache ActiveMQ Broker: before 5.19.11, from 6.0.0 before 6.3.2; Apache ActiveMQ All: before 5.19.11, from 6.0.0 before 6.3.2; Apache ActiveMQ: before 5.19.11, from 6.0.0 before 6.3.2. Defenders should prioritize verifying exposure and applying patches due to potential for authentication-based attacks. The vulnerability allows an authenticated client to spoof clientId when removing a durable topic subscription.

Defensive priority

Defenders should prioritize verifying exposure and applying patches due to potential for authentication-based attacks.

Recommended defensive actions

• Verify Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All versions for exposure
• Apply patches to upgrade to version 6.3.2 or 5.19.11
• Review authentication and authorization settings for TopicRegion
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability and affected versions. The vulnerability allows an authenticated client to spoof clientId when removing a durable topic subscription. Affected versions require verification and patching to version 6.3.2 or 5.19.11. Evidence is limited to CVE and NVD entries, and defenders should verify exposure and apply patches accordingly.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.