# CVE-2025-27391: Apache ActiveMQ Artemis: Passwords leaking from broker properties in the debug log

> Attackers with log access can read sensitive broker passwords if debug logging is enabled in Apache ActiveMQ Artemis.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-pm4j-p7pm-fpvx, ROOT-APP-MAVEN-CVE-2025-27391

## What is CVE-2025-27391?

CVE-2025-27391 is a medium-severity vulnerability in Apache ActiveMQ Artemis, published on 9 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insertion of Sensitive Information into Log File vulnerability in Apache ActiveMQ Artemis. All the values of the broker properties are logged when the org.apache.activemq.artemis.core.config.impl.ConfigurationImpl logger has the debug level enabled.

This issue affects Apache ActiveMQ Artemis: from 1.5.1 before 2.40.0. It can be mitigated by restricting log access to only trusted users.

Users are recommended to upgrade to version 2.40.0, which fixes the issue.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-27391?

2 open source packages ship an affected version, including org.apache.activemq:artemis-project. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.activemq:artemis-project` | Maven | From 1.5.1 | 2.40.0 |
| `org.apache.activemq:artemis-project` | Maven | From 1.5.1 | 2.40.0 |

Products: Apache Artemis.

## How do I fix CVE-2025-27391?

Upgrade org.apache.activemq:artemis-project to 2.40.0 or later.

## Is CVE-2025-27391 being exploited?

There is no known exploitation of CVE-2025-27391 in the wild and no public exploit code.

## Other vulnerabilities in Apache ActiveMQ Artemis

- [CVE-2026-57967](https://insights.sbomify.com/CVE-2026-57967/): Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment (critical 9.8)
- [CVE-2026-27446](https://insights.sbomify.com/CVE-2026-27446/): Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation (critical 9.3)
- [CVE-2026-49364](https://insights.sbomify.com/CVE-2026-49364/): Information disclosure in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2026-67593](https://insights.sbomify.com/CVE-2026-67593/): Missing authorization in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2023-50780](https://insights.sbomify.com/CVE-2023-50780/): Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27391 and fix it if it is affected.

What it is: CVE-2025-27391 is a medium-severity vulnerability in Apache ActiveMQ Artemis, published on 9 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27391 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.activemq:artemis-project (Maven): affected from 1.5.1; fixed in 2.40.0
- org.apache.activemq:artemis-project (Maven): affected from 1.5.1; fixed in 2.40.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27391/ (Markdown: https://insights.sbomify.com/CVE-2025-27391/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27391
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27391
- OSV: https://osv.dev/vulnerability/CVE-2025-27391

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27391/
Summaries are generated and may contain mistakes; the official description above is the record.