CVE-2026-1292

6.5 MEDIUM

📋 TL;DR

Tanium Trends logs sensitive information that should not be exposed. This vulnerability affects organizations using Tanium Trends who have access to log files containing this sensitive data.

💻 Affected Systems

Products:
  • Tanium Trends
Versions: Specific versions not provided in reference; consult Tanium advisory TAN-2026-007
Operating Systems: All platforms running Tanium Trends
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists when Tanium Trends is logging sensitive information that should be redacted.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers gain access to sensitive information like credentials, API keys, or internal system details from log files, leading to further compromise of the Tanium environment or connected systems.

🟠

Likely Case

Internal users with log access inadvertently view sensitive information, potentially violating compliance requirements or exposing operational details.

🟢

If Mitigated

With proper log access controls and monitoring, the exposed information remains protected from unauthorized access.

🌐 Internet-Facing: LOW - Log files are typically not internet-facing unless misconfigured.
🏢 Internal Only: MEDIUM - Internal users with log access could view sensitive information, but requires existing system access.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW - Requires access to log files containing the sensitive information.

Exploitation requires existing access to Tanium log files where the sensitive information is recorded.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Consult Tanium advisory TAN-2026-007 for specific patched versions

Vendor Advisory: https://security.tanium.com/TAN-2026-007

Restart Required: Yes

Instructions:

1. Review Tanium advisory TAN-2026-007. 2. Identify affected Tanium Trends versions. 3. Apply the Tanium-provided patch. 4. Restart Tanium services as required.

🔧 Temporary Workarounds

Restrict log file access

all

Limit access to Tanium log files to only authorized personnel.

# Linux: chmod 640 /var/log/tanium/*
# Windows: Configure ACLs on Tanium log directories

Implement log monitoring

all

Monitor access to Tanium log files for unauthorized attempts.

# Use file integrity monitoring or SIEM to track log file access

🧯 If You Can't Patch

  • Implement strict access controls on Tanium log directories and files
  • Regularly audit log file access and review for any sensitive information exposure

🔍 How to Verify

Check if Vulnerable:

Check Tanium Trends version against advisory TAN-2026-007 and review logs for unredacted sensitive information.

Check Version:

# On Tanium server: tanium version | grep Trends

Verify Fix Applied:

Verify Tanium Trends is updated to patched version per advisory and confirm sensitive information is no longer logged in plaintext.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to Tanium log files
  • Log entries containing sensitive information like passwords or keys

Network Indicators:

  • Unusual access patterns to log file locations

SIEM Query:

source="tanium_logs" AND (event_type="file_access" OR sensitive_data="*password*" OR sensitive_data="*key*")

🔗 References

📤 Share & Export