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.
CVE-2025-59868
Score 5.5 from GitHub Security Advisory published 2026-06-27. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 1.4%
- KEV
- Not listed
Published
June 27, 2026
Last Modified
July 6, 2026
Advisory Details (1)
Auto-updated Jun 27, 2026Security Bulletin: HCL Traveler for Microsoft Outlook (HTMO) is susceptible to sensitive data exposure (CVE-2025-59868) - Customer Support
https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0131419Vendor Advisories for CVE-2025-59868(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 55× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:00 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 12:38 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:27 UTCGHSA enrichment
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-14 16:18 UTCGHSA enrichment
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 18:09 UTCGHSA enrichment
- 2026-07-12 19:57 UTCGHSA enrichment
- 2026-07-11 21:48 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
Show 30 moreShow fewer
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 23:39 UTCGHSA enrichment
- 2026-07-10 01:30 UTCGHSA enrichment
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-09 03:19 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 04:59 UTCGHSA enrichment
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-07 06:50 UTCGHSA enrichment
- 2026-07-06 08:41 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 10:29 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 12:20 UTCGHSA enrichment
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-03 14:11 UTCGHSA enrichment
- 2026-07-02 16:03 UTCGHSA enrichment
- 2026-07-01 17:53 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 19:44 UTCGHSA enrichment
- 2026-06-29 21:35 UTCGHSA enrichment
- 2026-06-28 23:26 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-28 01:17 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEG score recompute
- 2026-06-27 03:08 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 95%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2025-59868?
When was CVE-2025-59868 disclosed?
Is CVE-2025-59868 actively exploited?
What is the CVSS score of CVE-2025-59868?
How do I remediate CVE-2025-59868?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-59868
Is Your Infrastructure Affected by CVE-2025-59868?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.