Tanium addressed an unauthorized code execution vulnerability in Threat Response.
Affects Tanium Threat Response before 4.9.480, 4.12.353, and 4.17.333 on endpoints running the Linux quarantine package. Fixed in Update 27 (v4.9.480) and later.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.9.480, 4.12.353, 4.17.333
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Threat Response prior to specified updates in 2025H1, 2025H2, and 2026H1 releases Execution is on endpoints running the Linux quarantine package
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
CVE-2026-116650 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Threat Response; fixed in 4.9.480, 4.12.353 and 4.17.333.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 4.9.480, 4.12.353, 4.17.333
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Tanium Threat Response, a security product used to detect and investigate threats on endpoints, is affected by this vulnerability. An attacker could exploit it to run unauthorized code on systems where the software is installed.
Read the original description
Tanium addressed an unauthorized code execution vulnerability in Threat Response.
What to do
Check whether your setup matches what the bug needs.
Affects Threat Response prior to specified updates in 2025H1, 2025H2, and 2026H1 releases Execution is on endpoints running the Linux quarantine packageUpgrade to a fixed version: 4.9.480, 4.12.353, 4.17.333.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Tanium Threat Response
From 4.9 · fixed in 4.9.480; From 4.12 · fixed in 4.12.353; From 4.17 · fixed in 4.17.333
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116650
Is CVE-2026-116650 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw lets unauthorized code run on endpoints that have the Linux quarantine package installed.Source: security.tanium.com
Which versions are affected by CVE-2026-116650?
Threat Response: from 4.9 before 4.9.480; from 4.12 before 4.12.353; from 4.17 before 4.17.333.Source: cve.now feed data
Am I affected, and how do I check?
Threat Response versions before 4.9.480 (from 4.9), before 4.12.353 (from 4.12), and before 4.17.333 (from 4.17) are affected, and only on endpoints running the Linux quarantine package. To check, compare the installed Threat Response version against these ranges and confirm whether the Linux quarantine package is present on the endpoint.Source: security.tanium.com
How do I fix CVE-2026-116650?
Update Threat Response to Update 27 (v4.9.480) or later, which is the fixed release listed for this vulnerability.Source: security.tanium.com