# CVE-2026-32642: Apache Artemis: Unauthorized Temporary Address Creation via OpenWire Protocol > Authenticated users can bypass address creation restrictions to temporarily create unauthorized addresses in Apache ActiveMQ Artemis. - **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Mar 2026 - **Updated:** 24 Mar 2026 - **Also known as:** GHSA-f4gc-mwrg-q36r, UBUNTU-CVE-2026-32642 ## What is CVE-2026-32642? CVE-2026-32642 is a low-severity missing authorization vulnerability in Apache ActiveMQ Artemis, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Incorrect Authorization (CWE-863) vulnerability in Apache Artemis, Apache ActiveMQ Artemis exists when an application using the OpenWire protocol attempts to create a non-durable JMS topic subscription on an address that doesn't exist with an authenticated user which has the "createDurableQueue" permission but does not have the "createAddress" permission and address auto-creation is disabled. In this circumstance, a temporary address will be created whereas the attempt to create the non-durable subscription should instead fail since the user is not authorized to create the corresponding address. When the OpenWire connection is closed the address is removed. This issue affects Apache Artemis: from 2.50.0 through 2.52.0; Apache ActiveMQ Artemis: from 2.0.0 through 2.44.0. Users are recommended to upgrade to version 2.53.0, which fixes the issue. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-32642? 4 open source packages ship an affected version, including org.apache.activemq:artemis-openwire-protocol and org.apache.artemis:artemis-openwire-protocol. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.activemq:artemis-openwire-protocol` | Maven | From 2.0.0 | 2.53.0 | | `org.apache.activemq:artemis-openwire-protocol` | Maven | From 2.0.0 | 2.53.0 | | `org.apache.artemis:artemis-openwire-protocol` | Maven | From 2.50.0 | 2.53.0 | | `org.apache.artemis:artemis-openwire-protocol` | Maven | From 2.50.0 | 2.53.0 | Products: Apache Artemis. ## How do I fix CVE-2026-32642? Upgrade org.apache.activemq:artemis-openwire-protocol to 2.53.0 or later. ## Is CVE-2026-32642 being exploited? There is no known exploitation of CVE-2026-32642 in the wild and no public exploit code. ## Other vulnerabilities in Apache ActiveMQ Artemis - [CVE-2026-57967](https://insights.sbomify.com/CVE-2026-57967/): Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment (critical 9.8) - [CVE-2026-27446](https://insights.sbomify.com/CVE-2026-27446/): Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation (critical 9.3) - [CVE-2026-49364](https://insights.sbomify.com/CVE-2026-49364/): Information disclosure in Apache ActiveMQ Artemis (critical 9.1) - [CVE-2026-67593](https://insights.sbomify.com/CVE-2026-67593/): Missing authorization in Apache ActiveMQ Artemis (critical 9.1) - [CVE-2023-50780](https://insights.sbomify.com/CVE-2023-50780/): Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32642 and fix it if it is affected. What it is: CVE-2026-32642 is a low-severity missing authorization vulnerability in Apache ActiveMQ Artemis, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32642 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.activemq:artemis-openwire-protocol (Maven): affected from 2.0.0; fixed in 2.53.0 - org.apache.activemq:artemis-openwire-protocol (Maven): affected from 2.0.0; fixed in 2.53.0 - org.apache.artemis:artemis-openwire-protocol (Maven): affected from 2.50.0; fixed in 2.53.0 - org.apache.artemis:artemis-openwire-protocol (Maven): affected from 2.50.0; fixed in 2.53.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32642/ (Markdown: https://insights.sbomify.com/CVE-2026-32642/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32642 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32642 - OSV: https://osv.dev/vulnerability/CVE-2026-32642 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32642/ Summaries are generated and may contain mistakes; the official description above is the record.