CVE-2025-27391 Vulnerability Analysis & Exploit Details

CVE-2025-27391
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2025-27391 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-27391 Details

Status: Analyzed

Last updated: 🕛 14 Jul 2025, 12:12 UTC
Originally published on: 🕒 09 Apr 2025, 15:16 UTC

Time between publication and last update: 95 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2025-27391 Vulnerability Summary

CVE-2025-27391: 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.

Assessing the Risk of CVE-2025-27391

Access Complexity Graph

The exploitability of CVE-2025-27391 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-27391

CVE-2025-27391 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-27391, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-27391, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-27391 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2025-27391 poses no threat to data integrity.
  • Availability: None
    CVE-2025-27391 does not impact system availability.

CVE-2025-27391 References

External References

CWE Common Weakness Enumeration

CWE-532

CAPEC Common Attack Pattern Enumeration and Classification

  • Fuzzing for application mapping CAPEC-215 An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.

Vulnerable Configurations

  • cpe:2.3:a:apache:activemq_artemis:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:1.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:1.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:1.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:1.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:1.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.19.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.19.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.23.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.23.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.26.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.26.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.27.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.27.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.28.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.28.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.30.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.30.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.31.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.31.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.31.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.31.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.31.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.31.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.32.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.32.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.33.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.33.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.34.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.34.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.35.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.35.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.36.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.36.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:activemq_artemis:2.37.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:activemq_artemis:2.37.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-27391: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-55613 – Tenda O3V2 1.0.0.12(3880) is vulnerable to Buffer Overflow in the fromSafeSetMacFilter function via the mac parameter.
  • CVE-2025-55581 – D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the mydlink-watch-dog.sh script. The scr...
  • CVE-2025-52287 – OperaMasks SDK ELite Script Engine v0.5.0 was discovered to contain a deserialization vulnerability.
  • CVE-2025-52085 – An SQL injection vulnerability in Yoosee application v6.32.4 allows authenticated users to inject arbitrary SQL queries via a request to a backend ...
  • CVE-2025-43760 – A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.4, 20...