Skip to main content

IBM CVE-2025-64647

| EUVDEUVD-2025-209033 MEDIUM
Use of a Cryptographic Primitive with a Risky Implementation (CWE-1240)
2026-03-25 ibm GHSA-42vr-vvgx-qhgx
5.9
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Cryptographic implementation review
Impact

The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates network-level attack surface with high attack complexity, no privilege requirement, and high confidentiality impact. The AC:H (high complexity) rating suggests the attacker must overcome significant technical barriers—likely requiring possession of encrypted material and computational resources to perform cryptanalysis or brute-force attacks. The absence of integrity and availability impact limits the vulnerability to passive information disclosure. While CVSS 5.9 sits in the medium range, the real-world risk depends heavily on EPSS score and exploitation maturity, which are not provided in the source data; however, the AC:H factor suggests this is not an easy exploit despite the high confidentiality impact. Organizations should prioritize patching based on whether sensitive data is encrypted with Concert and the exposure of encrypted artifacts to untrusted networks. This is a high-priority patch for institutions handling regulated data (PII, financial, healthcare) but lower urgency for those with strong network segmentation.

Exploit ScenarioDerived

An attacker with network access to Concert instances (either internal network access or via compromised credentials) captures encrypted sensitive data such as database connection strings or API keys that are encrypted using Concert's weak cryptographic implementation. Over weeks or months, the attacker performs offline cryptanalysis or brute-force attacks against the weak cipher, eventually recovering the plaintext credentials. These credentials are then used to access backend systems, causing secondary data breaches. The AC:H rating reflects the reality that this attack requires sustained effort and cryptographic knowledge, making it feasible only for determined or sophisticated threat actors rather than commodity malware.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

IBM Concert versions 1.0.0 through 2.2.0 implement cryptographic algorithms that are weaker than expected, allowing attackers to decrypt highly sensitive information without authentication. The vulnerability has a CVSS score of 5.9 with high confidentiality impact but no integrity or availability impact. A patch is available from IBM, and this represents a pure information disclosure risk affecting the confidentiality of encrypted data.

RemediationAI

Upgrade IBM Concert to a patched version released after 2.2.0 as detailed in the IBM support advisory at https://www.ibm.com/support/pages/node/7267105. Until patching is completed, implement network-level controls including network segmentation to restrict Concert instances to trusted internal networks only, disable any unnecessary cryptographic data export features, and review access logs for evidence of unauthorized decryption attempts. If re-encryption of existing sensitive data with Concert is possible, perform a cryptographic key rotation using stronger algorithms after patching. Ensure that encrypted artifacts stored in backups or archives are inventoried and scheduled for re-encryption post-patch.

Affected VersionsENISA

Concert 1.0.0 ≤2.2.0

Affected Packages

euvd concert no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability falls under CWE-1240 (Use of Insufficiently Trusted Data Source), which in this context refers to the use of cryptographic algorithms that do not provide adequate security strength. IBM Concert, an enterprise integration and orchestration platform, relies on cryptographic operations to protect sensitive configuration data, credentials, and inter-node communication. The weakness likely involves the use of deprecated or mathematically broken cryptographic primitives (such as weak key derivation functions, insufficient key lengths, or broken cipher suites) rather than modern standards like AES-256-GCM or ChaCha20-Poly1305. The affected CPE specification (cpe:2.3:a:ibm:concert:*:*:*:*:*:*:*:*) indicates all Concert products across all versions from 1.0.0 through 2.2.0 are impacted.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch released
Mar 25, 2026 - 20:47 nvd
Patch available
CVE Published
Mar 25, 2026 - 20:37 nvd
MEDIUM 5.9

DescriptionCVE.org

IBM Concert 1.0.0 through 2.2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information

Executive ViewAI

Why It Matters

CVE-2025-64647 presents moderate security risk rated CVSS 5.9. Exploitation could compromise the security of affected deployments. A patch is available and should be applied during regular vulnerability management.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy