Zero Day MonitorZDM
DashboardVulnerabilitiesTrendingZero-DaysNewsAbout
Login
ImpressumPrivacy Policy
Zero Day Monitor © 2026
3471 articles · 168586 vulns · 37/41 feeds (7d)
← Back to list
5.5
CVE-2025-59868
hcl · traveler for microsoft outlook

HCL Traveler for Microsoft Outlook (HTMO) is susceptible to sensitive data exposure

Description

HCL Traveler for Microsoft Outlook (HTMO) is susceptible to a sensitive data exposure vulnerability which could allow an attacker to exploit application information to then attempt additional attacks and cause unknown behavior in the application.

Affected Products

VendorProductVersions
hcltraveler for microsoft outlook<3.0.15

References

  • https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0131419

Related News (1 articles)

Tier C
VulDB2d ago
CVE-2025-59868 | HCL Traveler for Microsoft Outlook up to 3.0.14 log file (KB0131419)
→ No new info (linked only)
CVSS 3.15.5 MEDIUM
VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CISA KEV❌ No
Actively exploited❌ No
CWECWE-532
PublishedJun 27, 2026
Last enriched2d agov2
Trending Score15
Source articles1
Independent1
Info Completeness8/14
Missing: epss, kev, exploit, patch, iocs, mitre_attack

Community Vote

0
Login to vote
0 upvotes0 downvotes
No votes yet

Related CVEs (5)

HIGHPRE-CVE
Multiple vulnerabilities in HCL BigFix Compliance (Ruby) allowing code execution, security bypass, data manipulation, information disclosure, and denial of service
Trending: 27
MEDIUMCVE-2026-56457
HCL DevOps Deploy / HCL Launch is susceptible to an exposure of sensitive information
Trending: 23
HIGHCVE-2023-37524
HCL Traveler for Microsoft Outlook (HTMO) is susceptible to vulnerabilities due to .NET Framework 4.5 being out of service
Trending: 22
CRITICALCVE-2025-15619EXP
HCL Connections is vulnerable to broken access control
Trending: 21
MEDIUMCVE-2026-21768
HCL Verse for Android is susceptible to an injection vulnerability
Trending: 8

Pin to Dashboard

Verification

State: unverified
Confidence: 0%

Vulnerability Timeline

CVE Published
Jun 27, 2026
Discovered by ZDM
Jun 27, 2026
Updated: affectedVersions, severity
Jun 27, 2026

Version History

v2
Last enriched 2d ago
v2Tier C2d ago

Updated affected versions to include 3.0.14, changed severity to HIGH, and noted that no exploit exists.

affectedVersionsseverity
via VulDB
v12d ago

Initial creation