Quick answers
- Is CVE-2026-116651 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116651 being exploited in the wild.
- How severe is CVE-2026-116651?
- High severity, with a CVSS score of 7.5, published 3 November 2026.
- Which products and versions are affected?
- Tanium Threat Response 2025H1 prior to Update 27 (v4.9 to v4.9.480); 2025H2 prior to Update 17 (v4.12 to v4.12.353); 2026H1 prior to Update 10 (v4.17 to v4.17.333).
- Is there a fix for CVE-2026-116651?
- Yes: fixed in Threat Response 2025H1 Update 27 (v4.9.480), 2025H2 Update 17 (v4.12.353), 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-116651 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-116651?
- 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), 2025H2 Update 17 (v4.12.353), 2026H1 Update 10 (v4.17.333) and later
Technical details
An unauthorized code execution vulnerability exists in Tanium Threat Response's SSH Known Hosts sensor that can be exploited by authenticated users with Threat Response User and Interact Read-Only User roles. The vulnerability requires network access and authenticated credentials but does not require user interaction. Successful exploitation allows an attacker to execute arbitrary code on endpoints, potentially leading to full system compromise.
Affected products
- Tanium Threat Response 2025H1 prior to Update 27 (v4.9 to v4.9.480); 2025H2 prior to Update 17 (v4.12 to v4.12.353); 2026H1 prior to Update 10 (v4.17 to v4.17.333)
Timeline
- 2026-11-03: disclosed