Quick answers
- Is CVE-2026-87075 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87075 being exploited in the wild.
- How severe is CVE-2026-87075?
- High severity, with a CVSS score of 8.1, published 9 September 2026.
- Which products and versions are affected?
- Tanium Comply 2.32 to 2.32.252 (2025H1), 2.35 to 2.35.306 (2025H2), 2.37 to 2.37.308 (2026H1).
- Is there a fix for CVE-2026-87075?
- 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-87075 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-87075?
- 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 control issue in Tanium Comply that fails to properly validate authorization before allowing deletion operations. An authenticated user with the "comply report content write" permission can delete built-in vulnerability sources from the Comply database, affecting the integrity of vulnerability data. The attack requires network access and valid authentication credentials with specific permissions; no user interaction is needed beyond the malicious API calls. Patches are available: v2.32.252 or later (2025H1), v2.35.306 or later (2025H2), and v2.37.308 or later (2026H1). No workarounds are available.
Affected products
- Tanium Comply 2.32 to 2.32.252 (2025H1), 2.35 to 2.35.306 (2025H2), 2.37 to 2.37.308 (2026H1)
Timeline
- 2026-09-09: disclosed