VulnerabilityPublished 27 Oct 2026

CVE-2026-108331: Tanium Endpoint Configuration Toolset Solution · Uncontrolled Recursion

Affects Tanium Endpoint Configuration Toolset SolutionSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low · fixed in 1.71.25 : update Tanium Endpoint Configuration Toolset Solution when convenient.

Data as of 27 Oct 2026, 17:57 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.71.25, 1.59.50, 1.51.60 +5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
TaniumEndpoint Configuration Toolset Solution	Affected >=1.71.0 <1.71.25	Fixed in 1.71.25
TaniumEndpoint Configuration Toolset Solution	Affected >=1.59.0 <1.59.50	Fixed in 1.59.50
TaniumEndpoint Configuration Toolset Solution	Affected >=1.51.0 <1.51.60	Fixed in 1.51.60
Taniumthreat-response-cx	Affected >=1.21.1673 <1.21.1673	Fixed in 1.21.1673
Taniumthreat-response-cx	Affected >=1.20.2271 <1.20.2271	Fixed in 1.20.2271
Taniumthreat-response-cx	Affected >=1.19.2213 <1.19.2213	Fixed in 1.19.2213

AI-suggested

Fixed versions are available from Tanium, including 1.71.25, 1.59.50, 1.51.60, 1.21.1673, 1.20.2271, 1.19.2213, 1.18.2732, and 1.17.802. Users should upgrade to these versions or later to remediate the vulnerability. No additional mitigation steps are indicated.

Description

CVE-2026-108331 is an infinite loop vulnerability in the Tanium Endpoint Configuration Toolset Solution's Threat Response Client Extension. This flaw can cause uncontrolled recursion leading to a denial of service condition. Tanium has addressed this issue in fixed versions.

References

security.tanium.com/TAN-2026-063 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 17:45 UTC

Technical details

References

Community reviews

Related threats