Quick answers
- Is CVE-2026-116666 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116666 being exploited in the wild.
- How severe is CVE-2026-116666?
- Medium severity, with a CVSS score of 4.3, published 3 November 2026.
- Which products and versions are affected?
- Tanium Discover v4.10.0 to v4.10.204 (2025H1); v4.15.0 to v4.15.218 (2025H2); v4.19.0 to v4.19.137 (2026H1).
- Is there a fix for CVE-2026-116666?
- Yes: fixed in Discover v4.10.204 (2025H1 Update 26), v4.15.218 (2025H2 Update 16), v4.19.137 (2026H1 Update 9) and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116666 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116666?
- 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 (2025H1 Update 26), v4.15.218 (2025H2 Update 16), v4.19.137 (2026H1 Update 9) and later
Technical details
An improper access control vulnerability in Tanium Discover allows authenticated users with Discover Asset read permissions to access data outside their intended scope. The vulnerability requires network access and valid authentication credentials. An attacker gains read-only access to restricted asset information.
Affected products
- Tanium Discover v4.10.0 to v4.10.204 (2025H1); v4.15.0 to v4.15.218 (2025H2); v4.19.0 to v4.19.137 (2026H1)
Timeline
- 2026-11-03: disclosed