How severe is GHSA-w3w2-mpp5-92gm?

GHSA-w3w2-mpp5-92gm has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w3w2-mpp5-92gm?

GHSA-w3w2-mpp5-92gm affects the following packages: org.apache.activemq:apache-activemq (Maven), org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (Maven), org.apache.activemq:apache-activemq (Maven), org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w3w2-mpp5-92gm?

Update org.apache.activemq:apache-activemq to 5.19.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3w2-mpp5-92gm is resolved across your whole dependency graph.

How do I detect GHSA-w3w2-mpp5-92gm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:apache-activemq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w3w2-mpp5-92gm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w3w2-mpp5-92gm?

O3 pinpoints whether GHSA-w3w2-mpp5-92gm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w3w2-mpp5-92gm actively exploited in the wild?

No public exploit code has been indexed for GHSA-w3w2-mpp5-92gm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w3w2-mpp5-92gm?

GHSA-w3w2-mpp5-92gm has an EPSS (Exploit Prediction Scoring System) score of 4.8%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w3w2-mpp5-92gm?

GHSA-w3w2-mpp5-92gm is classified as Improper Input Validation (CWE-20), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-w3w2-mpp5-92gm?

A Nuclei detection template exists for GHSA-w3w2-mpp5-92gm, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-w3w2-mpp5-92gm published, and has it been updated?

GHSA-w3w2-mpp5-92gm was published on April 24, 2026 and was last updated on May 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-w3w2-mpp5-92gm

HIGH

GHSA-w3w2-mpp5-92gm is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in org.apache.activemq:apache-activemq. O3 Security confirms whether GHSA-w3w2-mpp5-92gm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache ActiveMQ Vulnerable to Improper Input Validation and Code Injection

Also known asBIT-activemq-2026-40466CVE-2026-40466

Published

Apr 24, 2026

Updated

May 14, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

4.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected

☕org.apache.activemq:apache-activemq☕org.apache.activemq:activemq-all☕org.apache.activemq:activemq-broker☕org.apache.activemq:apache-activemq☕org.apache.activemq:activemq-all☕org.apache.activemq:activemq-broker

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ.

An authenticated attacker may bypass the fix in CVE-2026-34197 by adding a connector using an HTTP Discovery transport via BrokerView.addNetworkConnector or BrokerView.addConnector through Jolokia if the activemq-http module is on the classpath. A malicious HTTP endpoint can return a VM transport through the HTTP URI which will bypass the validation added in CVE-2026-34197. The attacker can then use the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec().

This issue affects Apache ActiveMQ Broker: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ All: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5.

Users are recommended to upgrade to version 5.19.6 or 6.2.5, which fixes the issue.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:apache-activemq`	all versions	5.19.6
☕Maven	`org.apache.activemq:activemq-all`	all versions	5.19.6
☕Maven	`org.apache.activemq:activemq-broker`	all versions	5.19.6
☕Maven	`org.apache.activemq:apache-activemq`	≥ 6.0.0&&< 6.2.5	6.2.5
☕Maven	`org.apache.activemq:activemq-all`	≥ 6.0.0&&< 6.2.5	6.2.5
☕Maven	`org.apache.activemq:activemq-broker`	≥ 6.0.0&&< 6.2.5	6.2.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:apache-activemq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.activemq:apache-activemq to 5.19.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3w2-mpp5-92gm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w3w2-mpp5-92gm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w3w2-mpp5-92gm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. An authenticated attacker may bypass the fix in CVE-2026-34197 by adding a connector using an HTTP Discovery transport via BrokerView.addNetworkConnector or BrokerView.addConnector through Jolokia if the activemq-http module is on the classpath. A malicious HTTP endpoint can return a VM transport through the HTTP URI which will bypass the validation added in CVE-2026-34197. The attacker can then use the VM transport's brokerConfi

O3 Security · Impact-Aware SCA

Is GHSA-w3w2-mpp5-92gm in your dependencies?

O3 detects GHSA-w3w2-mpp5-92gm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works