Cyber Resilience

CVE-2025-36159

Ibm Concert 1.0.0 – 2.1.0

Published
20 November 2025
Modified
21 November 2025
Patch / advisory
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0011 2th percentile
Risk Priority 45 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-36159 is a medium-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Ibm Concert. Its CVSS base score is 6.2 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 2th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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 local user to forge log files to impersonate other users or hide their identity due to improper neutralization of output.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-52891Same product: Ibm Concert
CVE-2025-36081Same product: Ibm Concert
CVE-2025-1719Same product: Ibm Concert
CVE-2024-51451Same product: Ibm Concert
CVE-2025-1759Same product: Ibm Concert
CVE-2025-33083Same product: Ibm Concert
CVE-2025-1761Same product: Ibm Concert
CVE-2024-43180Same product: Ibm Concert
CVE-2024-52367Same product: Ibm Concert
CVE-2024-52366Same product: Ibm Concert

Affected Assets

ibm
concert
1.0.0 — 2.1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect output neutralization when log messages are constructed from untrusted input.

Input validation reduces the chance that specially crafted data reaches log-message construction routines.

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.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

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.

finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

prevents

Secure coding practices mandate input validation and output encoding, directly preventing log injection.

References