VulnerabilityPublished 27 Oct 2026

CVE-2026-108331: Threat Response Client Extension · Tanium Addressed an Infinite Loop Vulnerability

Source GCVE Database

Authoritative record:CVE-2026-108331· Low 3.3

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

Data as of 27 Oct 2026, 19:32 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.

ghsa-5jc2-gf6h-8mwf

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

Until a fix is confirmed, limit local access to trusted users and monitor for abnormal client extension behavior.

Description

An infinite loop vulnerability was identified and addressed in the Tanium Threat Response Client Extension. This flaw can cause a denial of service condition by making the affected component enter an endless processing loop.

Impact

The vulnerability impacts the availability of the Threat Response Client Extension by potentially causing it to enter an infinite loop, leading to denial of service. There is no impact on confidentiality or integrity. Exploitation requires local access with low privileges and no user interaction.

Summary

CVE-2026-108331 is an infinite loop vulnerability in the Tanium Threat Response Client Extension. The vulnerability can be triggered locally with low privileges and requires no user interaction. It impacts availability by causing the client extension to become unresponsive or consume excessive resources. The CVSS v3.1 base score is 3.3, indicating a low severity level.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 19:32 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats