Quick answers
- Is CVE-2026-87033 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87033 being exploited in the wild.
- How severe is CVE-2026-87033?
- 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.252 (2025H1), 2.35 to 2.35.306 (2025H2), 2.37 to 2.37.308 (2026H1).
- Is there a fix for CVE-2026-87033?
- 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-87033 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-87033?
- 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 boundaries when modifying network reports. An authenticated user possessing the "Comply Report Write" permission can modify any network report regardless of content set ownership, bypassing intended access restrictions. The attack requires valid Tanium credentials and the specific "Comply Report Write" permission. An attacker can achieve unauthorized modification of compliance data across the organization. Patches are available: Comply v2.32.252 and later (2025H1), v2.35.306 and later (2025H2), and v2.37.308 and later (2026H1).
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