CVE-2025-59868

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-27. a secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
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 computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 27, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated Jun 27, 2026
No patch confirmed yet.
generic

Security 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=KB0131419

Vendor 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 13× 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.

  1. 2026-07-28 15:35 UTCEPSS rescore
  2. 2026-07-28 14:33 UTCGHSA enrichment
  3. 2026-07-27 12:36 UTCEG score recompute
  4. 2026-07-27 12:36 UTCGHSA enrichment
  5. 2026-07-26 14:27 UTCEG score recompute
  6. 2026-07-26 14:27 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:00 UTCEG score recompute
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-21 15:24 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-16 12:38 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 14:27 UTCGHSA enrichment
  24. 2026-07-15 01:59 UTCEPSS rescore
  25. 2026-07-15 01:59 UTCEPSS rescore
Show 36 more
  1. 2026-07-14 16:18 UTCGHSA enrichment
  2. 2026-07-13 22:29 UTCEPSS rescore
  3. 2026-07-13 18:09 UTCGHSA enrichment
  4. 2026-07-12 19:57 UTCGHSA enrichment
  5. 2026-07-11 21:48 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 23:39 UTCGHSA enrichment
  9. 2026-07-10 01:30 UTCGHSA enrichment
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-09 03:19 UTCGHSA enrichment
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-08 04:59 UTCGHSA enrichment
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-07 06:50 UTCGHSA enrichment
  16. 2026-07-06 08:41 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 10:29 UTCGHSA enrichment
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 12:20 UTCGHSA enrichment
  22. 2026-07-04 06:30 UTCEPSS rescore
  23. 2026-07-03 14:11 UTCGHSA enrichment
  24. 2026-07-02 16:03 UTCGHSA enrichment
  25. 2026-07-01 17:53 UTCGHSA enrichment
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 19:44 UTCGHSA enrichment
  29. 2026-06-29 21:35 UTCGHSA enrichment
  30. 2026-06-28 23:26 UTCGHSA enrichment
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 04:55 UTCEPSS rescore
  34. 2026-06-28 01:17 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEG score recompute
  36. 2026-06-27 03:08 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-59868?
CVE-2025-59868 is a medium vulnerability published on June 27, 2026. 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.
When was CVE-2025-59868 disclosed?
CVE-2025-59868 was first published in the National Vulnerability Database on June 27, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-59868 actively exploited?
CVE-2025-59868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.6% of all scored CVEs.
What is the CVSS score of CVE-2025-59868?
CVE-2025-59868 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-59868?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-59868, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-59868

Explore →

Is Your Infrastructure Affected by CVE-2025-59868?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs