dbcve.org
ArtemisApplication · Apache

CVE-2025-27391

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 2.40.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Apache ActiveMQ Artemis versions 1.5.1 through 2.39.x, the ConfigurationImpl class logs all broker property values at debug level, which can expose sensitive configuration information such as credentials, connection strings, or other secrets into log files accessible to unauthorized users.

MitigationRestrict access to log files to trusted users only, or upgrade to version 2.40.0 which fixes this issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArtemisApplication
Affected:>= 1.5.1, < 2.40.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed Apache Artemis version
    Locate the Artemis installation and check the version file or manifest. Common locations include the lib folder or a version.properties file. Compare the version to the affected range: >= 1.5.1 and < 2.40.0
    Affected if The installed version is 1.5.1 through 2.39.x
  2. Verify if debug logging is enabled for the broker
    Examine the logging configuration file (such as log4j2.xml or logging.properties) for the logging level setting. Look for DEBUG level configuration on the broker classes, particularly ConfigurationImpl or general broker packages
    Affected if Debug (or TRACE) level logging is enabled for broker configuration classes
  3. Inspect broker configuration for sensitive properties
    Review the broker configuration files (such as broker.xml or artemis-queues.xml) for any credentials, connection strings, passwords, keystore passwords, or other secrets stored in plain text
    Affected if The broker configuration contains sensitive properties such as user credentials, connection strings with passwords, or other secrets
  4. Examine log files for exposed configuration data
    Search the Artemis log files for patterns that may indicate exposed sensitive data. Look for debug-level log entries containing property names like password, credential, secret, connectionString, or similar keywords in the log directory
    Affected if Log files contain sensitive configuration values (passwords, connection strings, secrets) in plain text at debug level

You are affected if your Apache Artemis version is between 1.5.1 and 2.39.x, you have debug logging enabled, and your broker configuration or logs contain sensitive credentials or secrets that could be exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.40.0 or later
Fixed in 2.40.0
Interim mitigation

Restrict access to log files to trusted users only, or upgrade to version 2.40.0 which fixes this issue.

Recommended fix High confidence

2.40.0

  1. Backup your existing Artemis installation and configuration files before upgrading
  2. Download Apache ActiveMQ Artemis version 2.40.0 from the official Apache distribution site
  3. Stop the running Artemis broker instance
  4. Install or extract version 2.40.0 to your target directory
  5. Restore your configuration from the backup
  6. Start the Artemis broker and verify it runs correctly
  7. Verify that broker properties are no longer logged at debug level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Artemis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27391 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data