Local memory disclosure via removed buffer clearing
Published Mar 25, 2026 · Updated Mar 25, 2026
Information disclosure in IBM Concert 1.0.0 through 2.2.0 allows local users to read sensitive data remaining in memory. A compiler removes buffer-clearing code, leaving sensitive contents in reusable memory instead of erasing them before release. Local access is required; the disclosed impact is limited to memory confidentiality, with no reported data modification or service interruption.
Summary
What happened
Information disclosure in IBM Concert 1.0.0 through 2.2.0 allows local users to read sensitive data remaining in memory. A compiler removes buffer-clearing code, leaving sensitive contents in reusable memory instead of erasing them before release. Local access is required; the disclosed impact is limited to memory confidentiality, with no reported data modification or service interruption.
The record
- CVE
- CVE-2025-64646
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- IBM
- Product
- Concert
- Classifications
- CWE-14, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record 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.2.0
What conditions does exploitation require?
What is affected?
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