Tanium Reputation up to 6.6.144/6.7.137/6.8.161 log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.98- |
Summary
A vulnerability identified as problematic has been detected in Tanium Reputation up to 6.6.144/6.7.137/6.8.161. This impacts an unknown function. This manipulation causes log file. This vulnerability appears as CVE-2026-108325. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability has been found in Tanium Reputation up to 6.6.144/6.7.137/6.8.161 and classified as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a log file vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Tanium addressed an insertion of sensitive information into log file vulnerability in Reputation.
The advisory is shared at security.tanium.com. This vulnerability is known as CVE-2026-108325 since 10/09/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 6.6.145, 6.7.138 or 6.8.162 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.6
CNA Vector (Tanium): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Reputation 6.6.145/6.7.138/6.8.162
Timeline
10/09/2026 CVE reserved10/27/2026 Advisory disclosed
10/27/2026 VulDB entry created
10/27/2026 VulDB entry last update
Sources
Advisory: security.tanium.comStatus: Confirmed
CVE: CVE-2026-108325 (🔒)
GCVE (CVE): GCVE-0-2026-108325
GCVE (VulDB): GCVE-100-427513
Entry
Created: 10/27/2026 18:57Changes: 10/27/2026 18:57 (62)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.