Local data disclosure via sensitive log entries
Published Jun 27, 2026 · Updated Jun 27, 2026
Sensitive-data exposure in HCL Traveler for Microsoft Outlook before 3.0.15 allows local users to read application information from logs. HTMO writes sensitive application information to log files, but HCL has not identified the responsible component or disclosed the logged fields. A local low-privileged account is required, and the documented consequence is disclosure that can support later attacks.
Summary
What happened
Sensitive-data exposure in HCL Traveler for Microsoft Outlook before 3.0.15 allows local users to read application information from logs. HTMO writes sensitive application information to log files, but HCL has not identified the responsible component or disclosed the logged fields. A local low-privileged account is required, and the documented consequence is disclosure that can support later attacks.
The record
- CVE
- CVE-2025-59868
- Published
- Jun 27, 2026
- Updated
- Jun 27, 2026
- Vendor
- HCLSoftware
- Product
- HCL Traveler for Microsoft Outlook
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 27, 2026CVE publishedPublication date reported by the CVE source.
- Jun 27, 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.0.15
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