Security Resilience

CVE-2025-36150

Crypto Weakness in Ibm Concert 1.0.0 – 2.0.0

Published
24 November 2025
Modified
08 October 2026
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0018 7th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-36150 is a medium-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Ibm Concert. Its CVSS base score is 5.9 (Medium).

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

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Concert 1.0.0 through 2.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-2024-52366Same product: Ibm Concert
CVE-2024-43189Same product: Ibm Concert
CVE-2025-33084Same product: Ibm Concert
CVE-2025-33102Same product: Ibm Concert
CVE-2024-51451Same product: Ibm Concert
CVE-2025-33015Same product: Ibm Concert
CVE-2024-49354Same product: Ibm Concert
CVE-2024-52367Same product: Ibm Concert
CVE-2024-43181Same product: Ibm Concert
CVE-2025-1761Same product: Ibm Concert

Affected Assets

ibm
concert
1.0.0 — 2.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-13 requires selection and implementation of specific cryptography types, directly stopping use of broken algorithms.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.24's policy, algorithm selection, strength/quality rules, approved standards and key management directly stop use of broken/risky algorithms in most cases; the bounded remainder is non-compliant implementations or legacy systems grandfathered under the clause's own regulatory and transition guidance.

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.

  • No fine-grained STIG row for CWE-327, a class-level weakness. Rules are authored against its narrower children: CWE-328, CWE-780, CWE-1240.

References