How severe is CVE-2011-4905?

No CVSS score has been assigned to CVE-2011-4905 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-4905?

CVE-2011-4905 affects the following packages: org.apache.activemq:activemq-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-4905?

Update org.apache.activemq:activemq-core to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4905 is resolved across your whole dependency graph.

How do I detect CVE-2011-4905 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:activemq-core. 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 CVE-2011-4905 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 CVE-2011-4905?

O3 pinpoints whether CVE-2011-4905 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 CVE-2011-4905 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2011-4905, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2011-4905?

CVE-2011-4905 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-4905 published, and has it been updated?

CVE-2011-4905 was published on January 5, 2012 and was last updated on April 10, 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

CVE-2011-4905

CVE-2011-4905 is a CWE-399 vulnerability in org.apache.activemq:activemq-core. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2011-4905 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in Apache ActiveMQ

Also known asGHSA-9wcx-326r-7j7w

Published

Jan 5, 2012

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

☕org.apache.activemq:activemq-core

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

Apache ActiveMQ before 5.6.0 allows remote attackers to cause a denial of service (file-descriptor exhaustion and broker crash or hang) by sending many openwire failover:tcp:// connection requests.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-core`	all versions	5.6.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Apache ActiveMQ before 5.6.0 allows remote attackers to cause a denial o…

issues.apache.orgNVDJan 2012

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:activemq-core. 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:activemq-core to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4905 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 CVE-2011-4905 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 CVE-2011-4905. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Apache ActiveMQ before 5.6.0 allows remote attackers to cause a denial of service (file-descriptor exhaustion and broker crash or hang) by sending many openwire failover:tcp:// connection requests.

O3 Security · Impact-Aware SCA

Is CVE-2011-4905 in your dependencies?

O3 detects CVE-2011-4905 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