Cyber Resilience

CVE-2025-36161

Crypto Weakness in Ibm Concert 1.0.0 – 2.1.0

Published
20 November 2025
Modified
24 November 2025
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.0021 11th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-36161 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 11th 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) and SC-8 (Transmission Confidentiality and Integrity) — 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 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict-Transport-Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-43178Same product: Ibm Concert
CVE-2024-55912Same product: Ibm Concert
CVE-2024-37070Same product: Ibm Concert
CVE-2024-45643Same product: Linux Linux Kernel
CVE-2024-45671Same product: Linux Linux Kernel
CVE-2023-38361Same product: Linux Linux Kernel
CVE-2023-30994Same product: Linux Linux Kernel
CVE-2023-26276Same product: Linux Linux Kernel
CVE-2025-33102Same product: Ibm Concert
CVE-2024-52366Same product: Ibm Concert

Affected Assets

ibm
concert
1.0.0 — 2.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-8 Transmission Confidentiality and Integrity
  • SC-13 Cryptographic Protection
  • AC-17 Remote Access
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires cryptographic protection of transmitted information to prevent MITM disclosure of sensitive data when HSTS is missing.

prevent

Mandates use of approved cryptographic mechanisms for protecting data in transit, directly countering the failure to enforce HTTPS via HSTS.

AC-17 Remote Access partial match
prevent

Requires encryption and integrity protections for all remote access sessions, mitigating the same MITM exposure described in the CVE.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.DS-01 partial match
prevents

PR.DS-01 promotes encryption for data-at-rest but never requires strong algorithms, leaving CWE-327 fully possible; the weakness is also far broader than data-at-rest so one narrow control removes none of its total risk.

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.

prevents

Mandating approved algorithms, cipher strength and usage standards directly stops the selection of broken or weak cryptographic primitives that attackers can exploit.

prevents

The explicit call-out of cryptography-related legal constraints (import/export, key escrow, digital-signature validity) reduces the likelihood that an organization will adopt broken or non-compliant cryptographic algorithms that violate those rules.

prevents

Access to current specialist guidance and early vulnerability alerts enables timely replacement of broken or risky cryptographic algorithms with stronger alternatives.

References