VulnerabilityPublished 25 Mar 2026

CVE-2025-64648: IBM Concert · Cleartext Transmission

Affects IBM ConcertSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: High
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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 29 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

Organizations should implement the following specific mitigations: 1) Upgrade IBM Concert to a version that addresses this vulnerability once IBM releases a patch or update. 2) Until a patch is available, enforce network-level encryption such as VPNs or TLS tunnels to protect data in transit. 3) Deploy network monitoring and intrusion detection systems to identify unusual MitM attack patterns or suspicious traffic. 4) Restrict IBM Concert usage to trusted, secure networks and avoid use over public or unsecured Wi-Fi. 5) Educate users about the risks of using the software on insecure networks and encourage the use of endpoint security controls. 6) Review and enforce strong access controls and authentication mechanisms to limit exposure if credentials are compromised. 7) Conduct regular security assessments and penetration tests focusing on network traffic to detect cleartext transmissions. These measures go beyond generic advice by focusing on compensating controls until a vendor patch is available and emphasizing network security hardening.

Description

IBM Concert 1.0.0 through 2.2.0 transmits data in clear text that could allow an attacker to obtain sensitive information using man in the middle techniques.

Impact

The primary impact of this vulnerability is the potential unauthorized disclosure of sensitive information transmitted by IBM Concert. Organizations using affected versions risk exposure of confidential data, including credentials and proprietary communications, which could lead to further compromise or espionage. Although the vulnerability does not affect data integrity or system availability, the confidentiality breach can undermine trust, cause regulatory compliance issues (e.g., GDPR, HIPAA), and lead to financial and reputational damage. The medium severity rating reflects the high complexity required to exploit the vulnerability, which may limit widespread attacks but does not eliminate risk, especially in environments with weak network security. Enterprises operating in sectors with high confidentiality requirements, such as finance, healthcare, and government, are particularly vulnerable. The lack of known exploits suggests the vulnerability is not yet actively targeted, but attackers could develop exploits given the cleartext transmission vector.

Summary

CVE-2025-64648 is a vulnerability identified in IBM Concert versions 1.0.0 through 2.2.0, where the application transmits sensitive information in cleartext over the network. This vulnerability is categorized under CWE-319, which involves the cleartext transmission of sensitive data. Because the data is not encrypted, an attacker positioned on the network path can perform man-in-the-middle (MitM) attacks to intercept and capture sensitive information such as authentication tokens, user credentials, or proprietary data. The CVSS v3.1 base score is 5.9 (medium severity), reflecting a network attack vector with high attack complexity, no privileges required, and no user interaction needed. The vulnerability affects confidentiality but does not impact integrity or availability. No patches or fixes have been linked yet, and no known exploits are reported in the wild, but the risk remains significant due to the nature of the data exposure. IBM Concert is widely used in enterprise collaboration, making the vulnerability relevant to organizations relying on this software for internal and external communications. The absence of encryption in data transmission is a critical security oversight that can be exploited in insecure or public networks, such as Wi-Fi hotspots or compromised internal networks.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
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-319

Technical details

References

Community reviews

Related threats