Skip to main content

IBM Concert CVE-2026-6930

| EUVDEUVD-2026-104488 LOW
Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
2026-10-19 psirt@us.ibm.com GHSA-wcgf-jf66-4mqx
3.7
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Intercept IBM Concert encrypted data
  2. Exploit
    Analyze weak cryptographic algorithm
  3. Impact
    Decrypt sensitive information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Approved algorithm selection
Exploitation Conditions

Exploitation requires the attacker to obtain the cryptographically protected data produced or stored by IBM Concert (versions 1.0 through 3.0.0) and then to overcome the weak algorithm to recover plaintext. The CVSS AC:H rating indicates this is not a single-step attack: it depends on the attacker gaining access to the ciphertext (e.g., via network capture or data-at-rest access) and expending cryptanalytic effort, which materially limits realistic exploitation. No authentication is required per PR:N, and no user interaction is needed (UI:N), but the confidentiality-only, high-complexity profile constrains impact to exposure of sensitive data rather than full system compromise.

Impact

This is a low-priority issue despite being network-exploitable. The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) yields a base score of 3.7 (LOW), and the signals are internally consistent: high attack complexity (AC:H) reflects that an attacker must capture encrypted data and then defeat the weak cryptographic algorithm (CWE-327), while impact is limited to a partial confidentiality loss (C:L) with no integrity or availability effect. No EPSS score, CISA KEV listing, SSVC decision data, or POC was provided in the input, so there is no evidence of active exploitation or published exploit code. No conflicting signals are present between the CVSS vector and the description - both point to a confidentiality-only cryptographic weakness requiring effort to exploit. The practical risk is that of a defense-in-depth cryptographic weakness rather than a readily weaponizable flaw; prioritize via normal patch cycles, not emergency response.

Exploit ScenarioDerived

An attacker positioned to capture encrypted data handled by IBM Concert (for example via network interception or access to stored ciphertext) exploits the use of a weaker-than-expected cryptographic algorithm to decrypt highly sensitive information. The high attack complexity (AC:H) means the attacker needs favorable conditions and cryptanalytic effort rather than a single trivial request. No public exploit code was identified in the provided data.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 19, 2026

IBM Concert 1.0 through 3.0.0 can expose highly sensitive information because it relies on weaker-than-expected cryptographic algorithms, allowing an attacker who obtains the protected data to attempt to recover plaintext. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) describes a network-reachable, unauthenticated and no-interaction path, but exploitation is high-complexity and limited to confidentiality impact. No CISA KEV entry and no public exploit were identified at time of analysis, so this is a low-priority cryptography hardening issue rather than an actively exploited intrusion vector.

RemediationAI

No vendor-released patch version is identified in the provided data; consult IBM's advisory at https://www.ibm.com/support/pages/node/7292374 for the fixed release and upgrade IBM Concert 1.0 through 3.0.0 as directed. Until a fixed build is confirmed, reduce exposure by preventing unnecessary storage or transmission of highly sensitive data under the affected weak cryptography, enforce stronger cryptographic configurations where the product allows algorithm selection, and restrict network and data-at-rest access to Concert-protected ciphertext through segmentation and least-privilege controls. These compensating controls lower the chance an attacker can obtain ciphertext but do not correct the underlying CWE-327 weakness, and tightening cryptography or access may break legacy integrations or require key and certificate rotation planning.

Affected VersionsENISA

Concert 1.0.0 ≤3.0.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

The root cause is CWE-327, use of a broken or risky cryptographic algorithm. In IBM Concert 1.0 through 3.0.0, the affected cryptographic protection is not strong enough to prevent decryption of highly sensitive information if an attacker can capture or otherwise access the ciphertext. The issue is not described as a protocol implementation flaw enabling direct remote code execution; the assessed vector is confidentiality-only (C:L) with high attack complexity (AC:H), no privileges (PR:N), and no user interaction (UI:N). Exploitation therefore depends on obtaining the protected data and expending cryptanalytic effort, which limits practical risk. No CPE mapping or public exploit data is provided.

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

Vendor (us) PRIMARY 3.7 LOW
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 3.7 LOW

Weak crypto exposes captured ciphertext, so AV:N/PR:N but AC:H for the cryptanalytic effort and positioning required; confidentiality-only C:L with no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

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

DescriptionCVE.org

IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
IBM Concert is a niche enterprise DevOps/observability product with limited deployment
Social Media
1
Sightings
Data Quality
5 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 LOW
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.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· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

18
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +18
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