Quick answers
- Is CVE-2026-116650 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116650 being exploited in the wild.
- How severe is CVE-2026-116650?
- High severity, with a CVSS score of 7.5, published 3 November 2026.
- Which products and versions are affected?
- Tanium Threat Response v4.9–v4.9.480 (2025H1), v4.12–v4.12.353 (2025H2), v4.17–v4.17.333 (2026H1).
- Is there a fix for CVE-2026-116650?
- Yes: fixed in Threat Response 2025H1 Update 27 (v4.9.480) and later, 2025H2 Update 17 (v4.12.353) and later, 2026H1 Update 10 (v4.17.333) and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116650 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116650?
- Check whether you run Tanium Threat Response 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: Threat Response 2025H1 Update 27 (v4.9.480) and later, 2025H2 Update 17 (v4.12.353) and later, 2026H1 Update 10 (v4.17.333) and later
Technical details
The vulnerability allows an authenticated user with Threat Response write permission to execute unauthorized code on Linux endpoints running the quarantine package, likely through a command injection or deserialization flaw in the Linux quarantine component. Attack requires network access and valid Tanium credentials with specific permissions; no user interaction is needed. A fix is available across all affected release branches.
Affected products
- Tanium Threat Response v4.9–v4.9.480 (2025H1), v4.12–v4.12.353 (2025H2), v4.17–v4.17.333 (2026H1)
Timeline
- 2026-11-03: disclosed