Security Resilience

CVE-2026-6719

Crypto Weakness in Ibm Concert 1.0.0 – 3.0.0

Published
19 October 2026
Modified
03 November 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0034 27th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-6719 is a high-severity Use of Insufficiently Random Values (CWE-330) vulnerability in Ibm Concert. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-36085Same product: Ibm Concert
CVE-2024-55909Same product: Ibm Concert
CVE-2025-36161Same product: Ibm Concert
CVE-2025-36081Same product: Ibm Concert
CVE-2025-33088Same product: Ibm Concert
CVE-2024-55912Same product: Ibm Concert
CVE-2026-6721Same product: Ibm Concert
CVE-2026-17472Same product: Ibm Concert
CVE-2026-3627Same product: Ibm Concert
CVE-2026-6794Same product: Ibm Concert

Affected Assets

ibm
concert
1.0.0 — 3.0.0

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-330

Key generation under controlled management uses approved random-bit sources rather than insufficiently random values.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

Cryptographic controls require use of approved, sufficiently random values for keys and nonces.

finds

Security testing can detect weak randomness but does not prescribe the control itself.

prevents

Secure coding standards explicitly prohibit use of weak or predictable random number generators.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References