# Apache Artemis: Unauthorized Temporary Address Creation via OpenWire Protocol

Advisory record · `GHSA-f4gc-mwrg-q36r`

- **Identifiers:** `GHSA-f4gc-mwrg-q36r` · `CVE-2026-32642`
- **State:** Confirmed
- **Severity:** CVSS 2.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 24 Mar 2026
- **Updated:** 26 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Mar 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.artemis:artemis-openwire-protocol` (Maven): affected `>=2.50.0, <2.53.0`; fixed in `2.53.0`
- `org.apache.activemq:artemis-openwire-protocol` (Maven): affected `>=2.0.0, <2.53.0`; fixed in `2.53.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Artemis artemis-openwire-protocol versions 2.50.0 through 2.52.0 and org.apache.activemq artemis-openwire-protocol versions 2.0.0 through 2.44.0 are affected. An authenticated user with the createDurableQueue permission but without createAddress can, when address auto-creation is disabled, create a temporary address by attempting a non-durable JMS topic subscription over OpenWire, which should have been refused. The temporary address is removed when the connection closes. Upgrade to version 2.53.0, which fixes the issue.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.3 Low, CVSS 4.0: `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`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f4gc-mwrg-q36r)

## Sources

- [GitHub Advisory Database: GHSA-f4gc-mwrg-q36r](https://github.com/advisories/GHSA-f4gc-mwrg-q36r)
- [OSV: GHSA-f4gc-mwrg-q36r](https://osv.dev/vulnerability/GHSA-f4gc-mwrg-q36r)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32642>
- <https://github.com/apache/artemis>
- <https://lists.apache.org/thread/4wlrp31ngq2yb54sf4kjb3bl41t4xgtp>
- <http://www.openwall.com/lists/oss-security/2026/03/20/2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f4gc-mwrg-q36r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f4gc-mwrg-q36r/>. Everything for agents: <https://agentprime.io/llms.txt>.