Quick answers
- Is CVE-2026-108302 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108302 being exploited in the wild.
- How severe is CVE-2026-108302?
- Medium severity, with a CVSS score of 4.3, published 27 October 2026.
- Which products and versions are affected?
- Tanium Comply 2025H1 (v2.32–v2.32.262), 2025H2 (v2.35–v2.35.322), 2026H1 (v2.37–v2.37.325).
- Is there a fix for CVE-2026-108302?
- Yes: fixed in Comply 2025H1 Update 26 (v2.32.263) and later; 2025H2 Update 16 (v2.35.323) and later; 2026H1 Update 9 (v2.37.326) and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108302 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-108302?
- Check whether you run Tanium Comply at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Comply 2025H1 Update 26 (v2.32.263) and later; 2025H2 Update 16 (v2.35.323) and later; 2026H1 Update 9 (v2.37.326) and later
Technical details
An improper access control vulnerability in Tanium Comply allows authenticated users with the "comply report content read" permission to gain read-only access to restricted data. The vulnerability requires network access and valid credentials (PR:L in CVSS), with no user interaction needed. A successful exploit results in unauthorized information disclosure.
Affected products
- Tanium Comply 2025H1 (v2.32–v2.32.262), 2025H2 (v2.35–v2.35.322), 2026H1 (v2.37–v2.37.325)
Timeline
- 2026-10-27: advisory