VulnerabilityPublished 24 Dec 2025

CVE-2025-36154: IBM Concert · Cleartext Storage in a File or on Disk

Affects IBM ConcertSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% 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:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Dec 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Concert	Affected =1.0.0	Fixed in–

AI-suggested

Since no official patches are currently available for CVE-2025-36154, European organizations should implement the following specific mitigations: 1) Restrict local access to build servers and developer workstations running IBM Concert to trusted personnel only, using strict access controls and role-based permissions. 2) Isolate Docker build environments in secure, ephemeral containers or virtual machines that are destroyed after use to prevent persistent storage of sensitive data. 3) Audit and review build scripts and configurations to ensure sensitive information is not written to disk in cleartext during recursive builds. 4) Employ encryption or secure vault solutions for managing secrets and credentials used in build processes, avoiding embedding them directly in build files. 5) Monitor filesystem access logs and use file integrity monitoring tools to detect unauthorized access or modifications to sensitive files. 6) Educate developers and DevOps teams about secure handling of secrets and the risks of cleartext storage. 7) Stay informed about IBM Concert updates and apply patches promptly once released. 8) Consider alternative orchestration tools with stronger security postures if immediate risk reduction is required. These measures go beyond generic advice by focusing on build environment isolation, access control, and secret management tailored to the nature of this vulnerability.

Description

IBM Concert 1.0.0 through 2.1.0 stores sensitive information in cleartext during recursive docker builds which could be obtained by a local user.

Impact

For European organizations, the primary impact of CVE-2025-36154 is the potential unauthorized disclosure of sensitive information stored by IBM Concert during Docker builds. This can lead to exposure of credentials, secrets, or proprietary configuration data, which could be leveraged for further attacks such as privilege escalation, lateral movement, or data breaches. The vulnerability affects confidentiality but does not compromise data integrity or system availability. Organizations using IBM Concert in development, testing, or production environments with shared or multi-user access are at higher risk. The impact is particularly significant in regulated industries such as finance, healthcare, and critical infrastructure, where data confidentiality is paramount. Additionally, organizations employing containerization and CI/CD pipelines may face increased exposure if build environments are not properly isolated. The lack of required privileges or user interaction means that even low-privileged local users or attackers who gain limited access could exploit this vulnerability. This could undermine trust in software supply chain security and increase compliance risks under GDPR and other data protection regulations.

CWE-313Cleartext Storage in a File or on Disk (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in a file, or on disk.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7255549 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Dec 2025, 19:25 UTC

WeaknessesCWE-313

Technical details

References

Community reviews

Related threats