CVE-2025-36159: IBM Concert · Log Injection
Affects IBM ConcertSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Concert | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-36159, European organizations should implement strict access controls to limit local user access to systems running IBM Concert, ensuring only trusted personnel can interact with the software. Employ enhanced monitoring and alerting for unusual log patterns or inconsistencies that may indicate log forgery attempts. Maintain comprehensive backups of log files to enable comparison and detection of tampering. Until IBM releases a patch, consider isolating IBM Concert instances in segmented network zones with restricted user access. Conduct regular audits of log integrity using cryptographic techniques such as log signing or hash chaining if supported by the environment. Educate system administrators and security teams about the risks of log manipulation and the importance of verifying log authenticity. Finally, stay informed on IBM’s advisories for patches or updates addressing this vulnerability and apply them promptly upon release.
Description
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.