Tanium Trends up to 3.10.19/3.11.78 log file

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Tanium Trends up to 3.10.19/3.11.78. Impacted is an unknown function. The manipulation leads to log file. This vulnerability is listed as CVE-2026-1292. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Tanium Trends up to 3.10.19/3.11.78. This issue affects an unknown functionality. The manipulation with an unknown input leads to a log file vulnerability. Using CWE to declare the problem leads to CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Impacted is confidentiality. The summary by CVE is:

Tanium addressed an insertion of sensitive information into log file vulnerability in Trends.

The advisory is shared at security.tanium.com. The identification of this vulnerability is CVE-2026-1292 since 01/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 3.10.20 or 3.11.79 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0466). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

• Tanium Endpoint Management

Productinfo

Vendor

• Tanium

Name

• Trends

Version

• 3.10.0
• 3.10.1
• 3.10.2
• 3.10.3
• 3.10.4
• 3.10.5
• 3.10.6
• 3.10.7
• 3.10.8
• 3.10.9
• 3.10.10
• 3.10.11
• 3.10.12
• 3.10.13
• 3.10.14
• 3.10.15
• 3.10.16
• 3.10.17
• 3.10.18
• 3.10.19
• 3.11.0
• 3.11.1
• 3.11.2
• 3.11.3
• 3.11.4
• 3.11.5
• 3.11.6
• 3.11.7
• 3.11.8
• 3.11.9
• 3.11.10
• 3.11.11
• 3.11.12
• 3.11.13
• 3.11.14
• 3.11.15
• 3.11.16
• 3.11.17
• 3.11.18
• 3.11.19
• 3.11.20
• 3.11.21
• 3.11.22
• 3.11.23
• 3.11.24
• 3.11.25
• 3.11.26
• 3.11.27
• 3.11.28
• 3.11.29
• 3.11.30
• 3.11.31
• 3.11.32
• 3.11.33
• 3.11.34
• 3.11.35
• 3.11.36
• 3.11.37
• 3.11.38
• 3.11.39
• 3.11.40
• 3.11.41
• 3.11.42
• 3.11.43
• 3.11.44
• 3.11.45
• 3.11.46
• 3.11.47
• 3.11.48
• 3.11.49
• 3.11.50
• 3.11.51
• 3.11.52
• 3.11.53
• 3.11.54
• 3.11.55
• 3.11.56
• 3.11.57
• 3.11.58
• 3.11.59
• 3.11.60
• 3.11.61
• 3.11.62
• 3.11.63
• 3.11.64
• 3.11.65
• 3.11.66
• 3.11.67
• 3.11.68
• 3.11.69
• 3.11.70
• 3.11.71
• 3.11.72
• 3.11.73
• 3.11.74
• 3.11.75
• 3.11.76
• 3.11.77
• 3.11.78

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion