Quick answers
- Is CVE-2026-116667 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116667 being exploited in the wild.
- How severe is CVE-2026-116667?
- Medium severity, with a CVSS score of 4.2, published 3 November 2026.
- Which products and versions are affected?
- Tanium Discover v4.10.0 to v4.10.204, v4.15.0 to v4.15.218, v4.19.0 to v4.19.137.
- Is there a fix for CVE-2026-116667?
- Yes: fixed in Discover v4.10.204, v4.15.218, v4.19.137 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116667 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116667?
- Check whether you run Tanium Discover 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: Discover v4.10.204, v4.15.218, v4.19.137 and later
Technical details
An improper access control vulnerability in Tanium Discover allows authenticated users holding the Discover Profile write permission to create and modify Discover scan actions without proper authorization checks. The vulnerability requires network access and valid authentication credentials but no elevated privileges beyond the basic Discover Profile write permission. A successful exploit grants the attacker the ability to modify scan configurations.
Affected products
- Tanium Discover v4.10.0 to v4.10.204, v4.15.0 to v4.15.218, v4.19.0 to v4.19.137
Timeline
- 2026-11-03: disclosed