Local information disclosure via cleartext build artifacts
Published Dec 24, 2025 · Updated Dec 24, 2025
Cleartext storage in IBM Concert 1.0.0 through 2.1.0 allows local users to obtain sensitive data from recursive Docker builds. During recursive Docker builds, Concert writes sensitive information to disk without protecting its confidentiality; IBM has not identified the file, data type, or responsible component. Reachability requires local access to build artifacts, and the reported impact is limited to reading exposed information.
Summary
What happened
Cleartext storage in IBM Concert 1.0.0 through 2.1.0 allows local users to obtain sensitive data from recursive Docker builds. During recursive Docker builds, Concert writes sensitive information to disk without protecting its confidentiality; IBM has not identified the file, data type, or responsible component. Reachability requires local access to build artifacts, and the reported impact is limited to reading exposed information.
The record
- CVE
- CVE-2025-36154
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- IBM
- Product
- Concert
- Classifications
- CWE-313, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <=2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo