What is CVE-2026-32642?

CVE-2026-32642 is a low-severity incorrect authorization vulnerability in org.apache.artemis:artemis-openwire-protocol (maven), affecting versions >= 2.50.0, < 2.53.0. It is fixed in 2.53.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

Which packages are affected by CVE-2026-32642?

org.apache.artemis:artemis-openwire-protocol (maven) versions >= 2.50.0, = 2.0.0, < 2.53.0.

Is there a fix for CVE-2026-32642?

Yes. CVE-2026-32642 is fixed in 2.53.0. Upgrade to this version or later.

Is CVE-2026-32642 exploitable, and should I be worried?

Whether CVE-2026-32642 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-32642 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-32642

Q: Which packages are affected by CVE-2026-32642?

org.apache.artemis:artemis-openwire-protocol (maven) versions >= 2.50.0, = 2.0.0, < 2.53.0.

Q: Is there a fix for CVE-2026-32642?

Yes. CVE-2026-32642 is fixed in 2.53.0. Upgrade to this version or later.

Q: Is CVE-2026-32642 exploitable, and should I be worried?

Whether CVE-2026-32642 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-32642 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-32642?

Upgrade: org.apache.artemis:artemis-openwire-protocol to 2.53.0 or later, org.apache.activemq:artemis-openwire-protocol to 2.53.0 or later.

Summary

Apache Artemis: Unauthorized Temporary Address Creation via OpenWire Protocol

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.

Impact

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Affected versions

org.apache.artemis:artemis-openwire-protocol (>= 2.50.0, < 2.53.0) org.apache.activemq:artemis-openwire-protocol (>= 2.0.0, < 2.53.0)

Security releases

org.apache.artemis:artemis-openwire-protocol → 2.53.0 (maven) org.apache.activemq:artemis-openwire-protocol → 2.53.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.artemis:artemis-openwire-protocol to 2.53.0 or later; org.apache.activemq:artemis-openwire-protocol to 2.53.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-32642? CVE-2026-32642 is a low-severity incorrect authorization vulnerability in org.apache.artemis:artemis-openwire-protocol (maven), affecting versions >= 2.50.0, < 2.53.0. It is fixed in 2.53.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
Which packages are affected by CVE-2026-32642?
- org.apache.artemis:artemis-openwire-protocol (maven) (versions >= 2.50.0, < 2.53.0)
- org.apache.activemq:artemis-openwire-protocol (maven) (versions >= 2.0.0, < 2.53.0)
Is there a fix for CVE-2026-32642? Yes. CVE-2026-32642 is fixed in 2.53.0. Upgrade to this version or later.
Is CVE-2026-32642 exploitable, and should I be worried? Whether CVE-2026-32642 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-32642 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-32642?
- Upgrade org.apache.artemis:artemis-openwire-protocol to 2.53.0 or later
- Upgrade org.apache.activemq:artemis-openwire-protocol to 2.53.0 or later