VulnerabilityPublished 10 Mar 2026

CVE-2026-21791: HCL Sametime · Sensitive Data in Logs

Affects HCL SametimeSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.3 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCLSametime	Affected =Android 12.0.21	Fixed in–

AI-suggested

To mitigate CVE-2026-21791, organizations should implement the following specific measures: 1) Restrict access to application logs on Android devices running HCL Sametime to trusted administrators only, using Android’s file permission controls and secure storage mechanisms. 2) Review and modify logging configurations within HCL Sametime, if possible, to disable or sanitize logging of sensitive hostname and URL information. 3) Employ mobile device management (MDM) solutions to enforce strict access controls and monitor log file access on managed devices. 4) Educate users and administrators about the risks of local privilege escalation and the importance of securing devices against unauthorized access. 5) Monitor for updates from HCL regarding patches or configuration changes that address this vulnerability and apply them promptly once available. 6) Consider network segmentation and endpoint security controls to limit the impact if device logs are compromised. These steps go beyond generic advice by focusing on controlling log access and minimizing sensitive data exposure within the specific context of HCL Sametime on Android.

Description

HCL Sametime for Android is impacted by a sensitive information disclosure. Hostnames information is written in application logs and certain URL

Impact

The primary impact of CVE-2026-21791 is the potential disclosure of sensitive hostname information and URLs through application logs. For organizations, this could lead to information leakage that assists attackers in mapping internal networks or identifying critical infrastructure components. While the vulnerability does not directly compromise system integrity or availability, the exposure of network-related data could be leveraged in multi-stage attacks or social engineering campaigns. The requirement for local privileges limits the scope of exploitation to scenarios where an attacker already has some level of access to the device, such as through physical access, malware with local execution rights, or insider threats. The absence of user interaction reduces the risk of exploitation via phishing or remote attacks. Overall, the impact is relatively low but should not be ignored in environments where sensitive communications or infrastructure details are handled via HCL Sametime on Android devices.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0129451 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 10:48 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats