CVE-2025-64645 Vulnerability Analysis & Exploit Details

CVE-2025-64645
Vulnerability Scoring

7.7
/10
Very High Risk

Highly exploitable, CVE-2025-64645 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-64645 Details

Status: Analyzed

Last updated: 🕠 29 Dec 2025, 17:38 UTC
Originally published on: 🕒 26 Dec 2025, 15:15 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

psirt@us.ibm.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-64645 Vulnerability Summary

CVE-2025-64645: IBM Concert 1.0.0 through 2.1.0 could allow a local user to escalate their privileges due to a race condition of a symbolic link.

Assessing the Risk of CVE-2025-64645

Access Complexity Graph

The exploitability of CVE-2025-64645 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-64645

With low attack complexity and no required privileges, CVE-2025-64645 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-64645, 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-64645, 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-64645 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-64645 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2025-64645 does not impact system availability.

CVE-2025-64645 References

External References

CWE Common Weakness Enumeration

CWE-367

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:a:ibm:concert:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.0.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.0.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:concert:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:concert:2.1.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-64645: 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-15531 – A vulnerability was identified in Open5GS up to 2.7.5. This vulnerability affects the function sgwc_bearer_add of the file src/sgwc/context.c. The ...
  • CVE-2025-15530 – A vulnerability was determined in Open5GS up to 2.7.6. This affects the function sgwc_s11_handle_create_indirect_data_forwarding_tunnel_request of ...
  • CVE-2026-0725 – The Integrate Dynamics 365 CRM plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and incl...
  • CVE-2025-8615 – The CubeWP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's cubewp_shortcode_taxonomy shortcode in all versions u...
  • CVE-2025-14078 – The PAYGENT for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.6. This is due to...