Unauthenticated heap-memory disclosure via uncleared allocations
Published Jan 20, 2026 · Updated Jan 20, 2026
Heap-memory disclosure in IBM Concert 1.0.0 through 2.1.0 allows remote attackers to read sensitive data from allocated memory. IBM has not identified the affected component or request path, but states that heap memory is not properly cleared before its contents become observable. Exploitation requires no authentication, has high attack complexity, and affects confidentiality without reported integrity or availability impact.
Summary
What happened
Heap-memory disclosure in IBM Concert 1.0.0 through 2.1.0 allows remote attackers to read sensitive data from allocated memory. IBM has not identified the affected component or request path, but states that heap memory is not properly cleared before its contents become observable. Exploitation requires no authentication, has high attack complexity, and affects confidentiality without reported integrity or availability impact.
The record
- CVE
- CVE-2025-1719
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- IBM
- Product
- Concert
- Classifications
- CWE-244, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 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.1.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