Quick answers
- Is CVE-2026-116647 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116647 being exploited in the wild.
- How severe is CVE-2026-116647?
- High severity, with a CVSS score of 7.1, published 27 October 2026.
- Which products and versions are affected?
- Tanium Comply 2.32 through 2.32.263 (2025H1), 2.35 through 2.35.323 (2025H2), 2.37 through 2.37.326 (2026H1).
- Is there a fix for CVE-2026-116647?
- Yes: fixed in Comply 2.32.263 (2025H1 Update 26), 2.35.323 (2025H2 Update 16), 2.37.326 (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-116647 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116647?
- Check whether you run Tanium Comply 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: Comply 2.32.263 (2025H1 Update 26), 2.35.323 (2025H2 Update 16), 2.37.326 (2026H1 Update 9) and later
Technical details
Improper output sanitization in Comply's CSV export feature allows injection of arbitrary data and formulas into exported files. An attacker with Tanium Client access can exploit this without authentication to inject malicious payloads that execute when the CSV is opened in a spreadsheet application, affecting confidentiality, integrity, and availability across system boundaries.
Affected products
- Tanium Comply 2.32 through 2.32.263 (2025H1), 2.35 through 2.35.323 (2025H2), 2.37 through 2.37.326 (2026H1)
Timeline
- 2026-10-27: disclosed