# CVE-2026-97867: ActiveMQ EJBd credential exposure in datasource lookup

Source: https://junglewise.ai/threats/cve-2026-97867-the-ejbd-remote-protocol-returns-datasource-connection-details  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-97867 · Severity: info · Published 2026-11-10

ActiveMQ's EJBd remote protocol exposes database credentials when clients look up datasources. An attacker with network access to the EJBd endpoint can retrieve database credentials and connect directly to the database, potentially leading to unauthorized data access or modification.

Technologies: [Apache ActiveMQ](https://junglewise.ai/threats/technologies/activemq). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-97867 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-97867 being exploited in the wild.

**How severe is CVE-2026-97867?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Apache ActiveMQ before 10.3.0 and before 11.0.0-M2.

**Is there a fix for CVE-2026-97867?** Yes: fixed in 10.3.0, 11.0.0-M2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-97867 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-97867?** Check whether you run Apache ActiveMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 10.3.0, 11.0.0-M2

## Technical details

The EJBd remote protocol in ActiveMQ returns datasource connection details including database credentials in response to datasource lookup requests from remote clients. An attacker with network connectivity to the EJBd endpoint can exploit this to extract credentials without authentication. A fix is available in versions 10.3.0 and 11.0.0-M2.

## Affected products

- Apache ActiveMQ before 10.3.0 and before 11.0.0-M2

## Timeline

- 2026-11-10: disclosed

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://lists.apache.org/thread/f6nqckc3wgqnnsrkb1hd640o3k4omfvr](https://lists.apache.org/thread/f6nqckc3wgqnnsrkb1hd640o3k4omfvr)

## Related threats

- [Apache ActiveMQ improper input validation in connection state handling](https://junglewise.ai/threats/cve-2026-108946-improper-input-validation-vulnerability-in-apache-activemq)
- [Apache ActiveMQ input validation bypass in LDAPAuthorizationMapPlugin](https://junglewise.ai/threats/cve-2026-108500-input-validation-vulnerability-in-apache-activemq-configured-to)
- [Apache ActiveMQ improper authorization cache invalidation](https://junglewise.ai/threats/cve-2026-111822-improper-invalidation-of-cached-authorizations-vulnerability-in)
- [Apache ActiveMQ improper input validation in durable subscriptions](https://junglewise.ai/threats/cve-2026-111821-improper-input-validation-vulnerability-in-apache-activemq)
- [Apache ActiveMQ memory leak in subscription handling](https://junglewise.ai/threats/cve-2026-108949-denial-of-service-via-oom-vulnerability-in-apache-activemq)
