# Apache Artemis has an Incorrect Authorization issue

Advisory record · `GHSA-rf99-f9j2-gv3f`

- **Identifiers:** `GHSA-rf99-f9j2-gv3f` · `CVE-2026-40914`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **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:** 28 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2026, 15:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.artemis:artemis-stomp-protocol` (Maven): affected `>=2.50.0, <2.54.0 || >=2.0.0, <=2.44.0`; fixed in `2.54.0`

## Machine-written summary

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

> Apache Artemis's artemis-stomp-protocol package, versions 2.50.0 through 2.53.0 and 2.0.0 through 2.44.0, is affected. A user with send or consume permission on an address via STOMP can change the address's routing type without the createAddress permission, allowing messages to be sent or consumed with a routing type that should have been rejected. Users should upgrade to version 2.54.0, which fixes the issue.

Written 2 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

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rf99-f9j2-gv3f)

## Sources

- [GitHub Advisory Database: GHSA-rf99-f9j2-gv3f](https://github.com/advisories/GHSA-rf99-f9j2-gv3f)
- [OSV: GHSA-rf99-f9j2-gv3f](https://osv.dev/vulnerability/GHSA-rf99-f9j2-gv3f)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40914>
- <https://github.com/apache/artemis/pull/6395>
- <https://github.com/apache/artemis/commit/53173375c4d5e4b57890e89d37ed8b666c974474>
- <https://github.com/apache/artemis>
- <https://issues.apache.org/jira/browse/ARTEMIS-5996>
- <https://lists.apache.org/thread/6q3st8dlorz2q05svqn11k1xl7jkmm4c>
- <http://www.openwall.com/lists/oss-security/2026/05/27/8>

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-rf99-f9j2-gv3f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rf99-f9j2-gv3f/>. Everything for agents: <https://agentprime.io/llms.txt>.