Sensitive log-data disclosure to privileged users
Published Jan 20, 2026 · Updated Jan 20, 2026
Sensitive information exposure in IBM Aspera Console 3.4.7 allows local users with high privileges to read data written to log files. IBM identifies the affected locus only as Console log files and has not disclosed which logging path writes the sensitive values or which values are recorded. Exploitation requires high privileges, and the documented consequence is limited to reading potentially sensitive logged information, with no reported data modification or service interruption.
Summary
What happened
Sensitive information exposure in IBM Aspera Console 3.4.7 allows local users with high privileges to read data written to log files. IBM identifies the affected locus only as Console log files and has not disclosed which logging path writes the sensitive values or which values are recorded. Exploitation requires high privileges, and the documented consequence is limited to reading potentially sensitive logged information, with no reported data modification or service interruption.
The record
- CVE
- CVE-2025-13925
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- IBM
- Product
- IBM Aspera Console
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- admin
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=3.4.7
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