VulnerabilityPublished 25 Mar 2026

CVE-2025-64646: IBM Concert · Compiler Removal of Code to Clear Buffers

Affects IBM ConcertSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMConcert	Affected >=1.0.0 <=2.2.0	Fixed in–
Mavencom.ibm/concert`pkg:maven/com.ibm/concert`Other threats	Affected =1.0.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:concert:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:concert:2.2.0:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-64646, organizations should implement strict local access controls to limit who can access systems running IBM Concert, ensuring only trusted users have local login capabilities. Employing endpoint security solutions that monitor for unauthorized memory access or suspicious local activity can help detect exploitation attempts. Organizations should audit and harden system configurations to reduce the attack surface, including disabling unnecessary local accounts and services. Until IBM releases an official patch, consider isolating IBM Concert systems in secure network segments with limited user access. Regularly review logs and system behavior for anomalies indicative of memory scraping or unauthorized access. Developers and administrators should be aware of this vulnerability and avoid storing sensitive data in memory longer than necessary. Once a patch becomes available, prioritize its deployment in all affected environments. Additionally, consider using memory protection technologies or runtime application self-protection (RASP) tools that can help prevent unauthorized memory reads.

Description

IBM Concert 1.0.0 through 2.2.0 could allow an attacker to access sensitive information in memory due to the buffer not properly clearing resources.

Impact

The primary impact of CVE-2025-64646 is the potential exposure of sensitive information residing in memory buffers that were not properly cleared due to compiler optimization removing the clearing code. This can lead to confidentiality breaches where attackers with local access can retrieve sensitive data such as credentials, cryptographic keys, or proprietary information. While the vulnerability does not affect system integrity or availability, the exposure of confidential data can facilitate further attacks, including privilege escalation or lateral movement within an organization’s network. The requirement for local access limits the scope of exploitation, but insider threats or attackers who have gained initial footholds could exploit this vulnerability to escalate their access or exfiltrate sensitive data. Organizations relying on IBM Concert in environments with multiple users or less stringent local access controls are at higher risk. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability becomes widely known. The impact is significant for sectors handling sensitive or regulated data, including finance, government, healthcare, and critical infrastructure.

CWE-14Compiler Removal of Code to Clear Buffers (opens in a new tab)
Variant weakness
Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal."
Implementation
Store the sensitive data in a "volatile" memory location if available.
Build and Compilation
If possible, configure the compiler so that it does not remove dead stores.
Architecture and Design
Where possible, encrypt sensitive data that are used by a software system.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7267105 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 25 Mar 2026, 21:02 UTC

WeaknessesCWE-14

Technical details

References

Community reviews

Related threats