CVE-2025-15332
Information Disclosure Vulnerability in Tanium Threat Response
Publication date: 2026-02-05
Last updated on: 2026-02-10
Assigner: Tanium
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tanium | threat_response | From 4.5.0 (inc) to 4.5.250 (exc) |
| tanium | threat_response | From 4.6.0 (inc) to 4.6.518 (exc) |
| tanium | threat_response | From 4.9.0 (inc) to 4.9.297 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-532 | The product writes sensitive information to a log file. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-15332 is an information disclosure vulnerability in Tanium Threat Response. It allows an authenticated user with the "Threat Response Audit - Read" permission to access data beyond their authorized scope in a read-only manner.'}, {'type': 'paragraph', 'content': 'This flaw affects versions of Threat Response prior to 4.9.297, 4.6.518, and 4.5.250, and has been fixed in these versions and later.'}] [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information to users who should not have access to it, potentially exposing confidential data.
Since the access is read-only, it does not allow modification or disruption of data, but the confidentiality of information is compromised.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or methods provided to identify this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Tanium Threat Response to version 4.9.297, 4.6.518, 4.5.250 or later, as these versions have addressed the issue.
There are no available workarounds or other mitigations.