Tanium addressed a compression bomb vulnerability in Findings.

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Tanium/Findings (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Tanium/Findings.
2. 2Review the reported fix. Update Tanium/Findings to 1.2.95 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 19, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 19, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 19, 2026

Sources and claim methodology

• Source referencesecurity.tanium.com

Related CVEs

• Tina: Cross-origin `POST /media/upload/*` requests can write arbitrary files into the Tina dev server media rootSame generic ecosystem
• Path Traversal through Universal Forwarder Installer Archive Extraction in Splunk SOARSame generic ecosystem
• Information Disclosure through Missing Authorization in the Health REST API in Splunk SOARSame generic ecosystem
• Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOARSame generic ecosystem
• Improper Certificate Validation through CyberArk Vault Privileged Access Manager in Splunk SOARSame generic ecosystem
• Structured Query Language Injection through the REST API in Splunk SOARSame generic ecosystem