Quick answers
- Is CVE-2026-87025 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87025 being exploited in the wild.
- How severe is CVE-2026-87025?
- Medium severity, with a CVSS score of 5.4, published 9 September 2026.
- Which products and versions are affected?
- Tanium Comply 2.32 to 2.32.251; 2.35 to 2.35.305; 2.37 to 2.37.307.
- Is there a fix for CVE-2026-87025?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-87025 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-87025?
- 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.
Technical details
The vulnerability is an improper access controls flaw in Tanium Comply that fails to properly validate content set ownership when handling credential operations. An authenticated user with the Comply Credential Write permission can create or modify credentials belonging to a different content set than their own, bypassing intended access restrictions. The attack requires valid authentication and the target permission but no user interaction. Exploitation allows credential hijacking and lateral movement across different organizational contexts. Patches are available for all affected release lines: v2.32.252 (2025H1), v2.35.306 (2025H2), and v2.37.308 (2026H1).
Affected products
- Tanium Comply 2.32 to 2.32.251; 2.35 to 2.35.305; 2.37 to 2.37.307
Timeline
- 2026-09-09: disclosed