Quick answers
- Is CVE-2026-116660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116660 being exploited in the wild.
- How severe is CVE-2026-116660?
- Medium severity, with a CVSS score of 4.3, published 27 October 2026.
- Which products and versions are affected?
- Tanium Enforce 2.9 to 2.9.736, 2.10 to 2.10.778, 3.0 to 3.0.373.
- Is there a fix for CVE-2026-116660?
- Yes: fixed in Enforce 2.9.736 (2025H1 Update 26), 2.10.778 (2025H2 Update 16), 3.0.373 (2026H1 Update 9). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116660 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116660?
- Check whether you run Tanium Enforce 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: Enforce 2.9.736 (2025H1 Update 26), 2.10.778 (2025H2 Update 16), 3.0.373 (2026H1 Update 9)
Technical details
An improper access controls vulnerability in Tanium Enforce allows authenticated users with the Enforce Policy Read permission to read data beyond their authorized scope. The vulnerability affects versions 2.9 through 3.0, requiring network access and valid user credentials with specific permissions to exploit. An attacker gains read-only access to restricted data.
Affected products
- Tanium Enforce 2.9 to 2.9.736, 2.10 to 2.10.778, 3.0 to 3.0.373
Timeline
- 2026-10-27: disclosed