Read the docs

Tanium Threat Response writes sensitive information into a log file

Priority LOW 19CWE-532Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Required
Attack complexity
High
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-532.

Summary

Tanium Threat Response from 4.9 before 4.9.476, from 4.12 before 4.12.349, and from 4.17 before 4.17.327 writes sensitive information into a log file, a weakness classified as CWE-532. An attacker with high privileges on the network needs a user to interact with the product before the sensitive data can be read from the log, which gives high confidentiality impact.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00231 14th percentileScored 2026-11-07
Fix Fixed Threat Response (Tanium): 4.9.476, 4.12.349, 4.17.327

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
TaniumThreat Response4.9 to before 4.9.476; 4.12 to before 4.12.349; 4.17 to before 4.17.3274.9.476, 4.12.349, 4.17.327Patch availableCNA
  • Threat Response VendorTanium Affected 4.9 to before 4.9.476; 4.12 to before 4.12.349; 4.17 to before 4.17.327 Fixed in 4.9.476, 4.12.349, 4.17.327 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:tanium:threat_response:*:*:*:*:*:*:*:*——Tanium
  • cpe:2.3:a:tanium:threat_response:*:*:*:*:*:*:*:* Versions — — ·Tanium

Remediation

Upgrade Tanium Threat Response to 4.9.476, 4.12.349, or 4.17.327 or later, depending on the release branch in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA Threat Response (Tanium) Fixed in 4.9.476, 4.12.349, 4.17.327

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Tanium Threat Response 4.12.349, 4.17.327, 4.9.476

    2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW

    Other records, highest priority first

    • TI-2026-81473 Unauthorized code execution in Tanium Threat ResponsePriority MEDIUM 41

Timeline

  1. 2026-10-27 Threatist record created from CVE-2026-108328
  2. 2026-10-27 Alias added: GHSA-g9x9-6598-cgxj
  3. 2026-11-04 CISA SSVC decision points changed

References

  • TI-2026-81473 Unauthorized code execution in Tanium Threat Response CVSS 3.1HIGH 8.8
  • TI-2026-81459 Tanium Certificate Manager unauthorized code execution vulnerability CVSS 3.1HIGH 8.8
  • TI-2026-59476 Tanium addressed a SQL injection vulnerability in Threat Response. CVSS 3.1HIGH 8.8
  • TI-2026-08094 Tanium addressed an unauthorized code execution vulnerability in Connect. CVSS 3.1HIGH 8.8
  • TI-2026-08093 Tanium addressed an unauthorized code execution vulnerability in Connect. CVSS 3.1HIGH 8.8
  • TI-2025-13983 Tanium addressed an improper input validation vulnerability in Deploy. CVSS 3.1HIGH 8.8
See all 135 →

Sources