HCL Traveler for Microsoft Outlook EUVD-2026-45141

Exploitation requires three concurrent conditions: (1) local access to the Windows host running HCL Traveler for Microsoft Outlook, (2) high-privilege (PR:H) OS-level access sufficient to write or replace files within a directory in HTMO's DLL search path - on a properly hardened Windows system this typically means administrator rights - and (3) user interaction (UI:R), specifically a user launching Microsoft Outlook or triggering HTMO initialization to cause the malicious DLL to be loaded. Remote or unauthenticated exploitation is not possible. Standard unprivileged local users on a correctly configured Windows host cannot place files in protected application directories without first independently escalating privileges, which is the primary limiting factor for real-world exploitation. No specific non-default configuration setting is identified as a prerequisite in available data beyond the standard HTMO installation on Windows.

The CVSS 6.5 medium score accurately reflects the constrained exploitability profile. AV:L eliminates any remote or network-based attack path; the threat actor must already have interactive or shell-level access to the target Windows host. PR:H further narrows the field - the attacker requires administrator-level or equivalent privileges to write into protected application directories on a properly configured Windows system. UI:R adds a third barrier: a user must actively launch or interact with HTMO to trigger the malicious DLL load. Despite these prerequisites, the C:H/I:H/A:H impact metrics are appropriate, as successful DLL injection yields full code execution within the application's trust context. No EPSS score was provided in the input data, so probabilistic exploitation likelihood cannot be quantified. The absence of KEV listing and no identified public exploit code means this is not currently observed in active campaigns. In practice, this vulnerability is primarily relevant as a privilege escalation step or persistence mechanism for an attacker who has already achieved elevated local access - it does not represent an initial compromise vector.

A local attacker who has already obtained administrator-level credentials on a Windows host running HTMO - for example, through a previous credential theft or privilege escalation - identifies a DLL loaded by the application and places a trojanized version in a directory earlier in HTMO's search path than the legitimate copy. When a user subsequently launches Microsoft Outlook or the HTMO add-in initializes, the malicious DLL is loaded into the HTMO process, executing attacker-controlled code with the full confidentiality, integrity, and availability impact of the application's trust level. No public exploit code has been identified at time of analysis.