CVE-2026-32642
Incorrect Authorization in Apache Artemis OpenWire Address Creation
Publication date: 2026-03-24
Last updated on: 2026-03-30
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | activemq_artemis | From 2.0.0 (inc) to 2.44.0 (inc) |
| apache | artemis | From 2.50.0 (inc) to 2.53.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32642 is an Incorrect Authorization vulnerability in Apache Artemis and Apache ActiveMQ Artemis when using the OpenWire protocol.
It happens when an authenticated user who has the permission to create durable queues but lacks permission to create addresses tries to create a non-durable JMS topic subscription on an address that does not exist, while address auto-creation is disabled.
Instead of denying this operation due to insufficient permissions, the system incorrectly creates a temporary address. This temporary address is removed once the OpenWire connection is closed.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized creation of temporary addresses in the messaging system, which should not occur without proper permissions.
While the impact is considered low severity, it may allow users to bypass intended authorization controls temporarily, potentially leading to unexpected behavior or resource usage in the messaging infrastructure.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate step to mitigate this vulnerability is to upgrade Apache Artemis or Apache ActiveMQ Artemis to version 2.53.0 or later, where the issue is fixed.