Quick answers
- Is CVE-2026-87037 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87037 being exploited in the wild.
- How severe is CVE-2026-87037?
- Medium severity, with a CVSS score of 5.4, published 9 September 2026.
- Which products and versions are affected?
- Tanium Comply 2.32–2.32.251 (2025H1); 2.35–2.35.305 (2025H2); 2.37–2.37.307 (2026H1).
- Is there a fix for CVE-2026-87037?
- 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-87037 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-87037?
- 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 allows authenticated users with the "comply report write" permission to bypass intended authorization checks. The flaw affects multiple release branches: 2025H1 (v2.32–v2.32.251), 2025H2 (v2.35–v2.35.305), and 2026H1 (v2.37–v2.37.307). Exploitation requires valid Tanium credentials and the specific report-write permission; no network authentication or user interaction is required beyond the initial login. An attacker can read and write data outside their authorized scope, compromising data integrity and confidentiality. Patches are available via product updates in all affected release branches.
Affected products
- Tanium Comply 2.32–2.32.251 (2025H1); 2.35–2.35.305 (2025H2); 2.37–2.37.307 (2026H1)
Timeline
- 2026-09-09: disclosed