# Apache ActiveMQ Vulnerable to Improper Input Validation and Code Injection

Advisory record · `GHSA-w3w2-mpp5-92gm`

- **Identifiers:** `GHSA-w3w2-mpp5-92gm` · `BIT-activemq-2026-40466` · `CVE-2026-40466`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 24 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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

## Affected packages

- `org.apache.activemq:apache-activemq` (Maven): affected `<5.19.6 || >=6.0.0, <6.2.5`; fixed in `5.19.6`, `6.2.5`
- `org.apache.activemq:activemq-all` (Maven): affected `<5.19.6 || >=6.0.0, <6.2.5`; fixed in `5.19.6`, `6.2.5`
- `org.apache.activemq:activemq-broker` (Maven): affected `<5.19.6 || >=6.0.0, <6.2.5`; fixed in `5.19.6`, `6.2.5`

## Machine-written summary

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

> Apache ActiveMQ (apache-activemq, activemq-all and activemq-broker) versions before 5.19.6 and from 6.0.0 before 6.2.5 are vulnerable. An authenticated attacker can bypass an earlier fix by adding a connector that uses an HTTP discovery transport through Jolokia, which can lead to remote code execution on the broker's JVM. Upgrade to 5.19.6 or 6.2.5.

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

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

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

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w3w2-mpp5-92gm)

## Sources

- [GitHub Advisory Database: GHSA-w3w2-mpp5-92gm](https://github.com/advisories/GHSA-w3w2-mpp5-92gm)
- [OSV: GHSA-w3w2-mpp5-92gm](https://osv.dev/vulnerability/GHSA-w3w2-mpp5-92gm)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40466>
- <https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt>
- <https://github.com/apache/activemq>

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-w3w2-mpp5-92gm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w3w2-mpp5-92gm/>. Everything for agents: <https://agentprime.io/llms.txt>.